Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Info

Download releases from the support site, support.flexagon.com.

FlexDeploy 4.0.3 - Patch Release 10-19-2017

General/Usability

  • For Partial Deploy projects when performing Build All Files request, populated files will be sorted as per FD_ORDER.seq file in project root folder in SCM.

FlexDeploy 4.0.3 - Patch Release 08-28-2017

...

FlexDeploy 4.0.3 - Patch Release 07-19-2017

General/Usability

  • Increase the length of the Project Name field from 50 to 100 characters.

...

FlexDeploy 4.0.3 - Patch Release 06-29-2017

General/Usability

  • Fix for TFVC Build and Populate sometimes throwing error, especially if multiple checkouts were performed simultaneously.
  • Fix for Invisible FlexFields being visible on Application Request Form.
  • Fix for abort button not closing the ssh connection properly.
  • Better error when Endpoint Instance override setting is wrong in a workflow.

...

FlexDeploy 4.0.3 - Patch Release 06-14-2017

General/Usability

  • Added new variables in Workflow Execution Context for FD_WORKFLOW_REQUEST_ID and FD_WORKFLOW_EXECUTION_ID.

  • Fix for create Approval button on Folder/Application Configuration page was not enabled for users with Update Approval permissions. It was available to FlexDeploy Administrators.

  • Added MainStream variable to FlexField Validation Groovy Script.

  • Test instances were incorrectly marked as not Deployment Target.

  • REST API fix - Package Name is not unique anymore so allowing user to provide ProjectVersion or UseLatestPackageVersion flag.

  • New properties added to ServiceNow instance to allow customization of Approval and Rejection logic for Change Tickets.

  • Fix for NullPointerException in flexagon.fd.model.script.PropertyValueEvaluator.evaluatePropertyExpressions where empty expression is set for Property values.

  • Fix for JIRA integration fails with java.lang.NoClassDefFoundError: org/apache/commons/lang/StringEscapeUtils.

  • Added xls extension to file names and removed space in file name for all Report export to excel operations.

  • Added CMS integration (ServiceNow) and external approval support when deploying at application level.

  • Environment history and state report was not showing external tickets for ITS and folder request.

  • Fix for - groovy.lang.MissingPropertyException: No such property: InstanceCode for class: Script1, when performing application level build.

  • Approval and Scheduled tasks pages have link now for Application Request as well, so approver can easily look at details of Request.
  • Fix for version name was not being displayed in Scheduled Tasks page for project details.

...

FlexDeploy 4.0.3 - Patch Release 05-22-2017

General/Usability

  • FlexFields
    • FlexFields for Build or Deploy request can now be setup to be invisible. This will allow for custom validations to be executed prior to submit of request. Variables supported in FlexFields groovy validation scripts are - EnvironmentCode, InstanceCodes, ProjectName, ApplicationName, FolderPath, PartialDeploymentsFlag, ProjectType, WorkflowName, PackageName, StartTime, StreamName, StreamAttribute1, StreamAttribute2, StreamAttribute3, BuildEnvironmentCode, BuildInstanceCode, UserName, UserRoles, Force, ExceptionToWindow, TriggerType, Value, ValidationMessage.

      • For example, if you want to require Package Name (optional by default), you can configure an invisible FlexField to perform such validation.

    • Build request FlexFields are associated with the Project Version and stored in database. Now they are visible on the Approval and Scheduled Tasks table, so that the approver can make decisions based on those values. In addition, build request FlexFields are also visible on various reports.
  • Approval and Scheduled Tasks
    • Package Name is now displayed for each request.
    • Request Id is now link which will allow the approver to view details of the request (like Included Files) prior to approving the request.
    • Build request FlexFields are visible now for each request waiting for approval or schedule.
  • Partial Deployment Projects
    • Package Name is no longer a unique constraint. Users can reuse the same Package Name for many builds. Each build request will still have unique Project Version. This will allow users to rebuild the Package over time before eventually deploying to down-stream environments.
      • Re-build Package with Same Files option will default Package Name to the same as the previous package name for which user clicked Re-build Gear icon.
      • Project Version and Created by is now displayed on various screens along with Package Name, which should give users more visibility into the package details.
    • Added new permission - Configure Commands to allow control of who can update Build and Deploy commands for Project Files. This was previously limited to FlexDeploy Administrators.
    • Edit and Inactivate icons on Project Files screen are now available on left side as well so that user does not have to scroll all the way to right to perform those actions.
  • Project Properties - Override Property button does not lose values entered on the screen.
  • Tomcat server failed to stop in some cases with shutdown scripts as SSH threads did not terminate correctly. This issue is now resolved.
  • Build or Deploy notification email now includes Project Version or Package Name along with Request Id.

...

FlexDeploy 4.0.3 - Patch Release 05-11-2017

General/Usability

  • Project Files screen

    • Evaluate on Functional Setup was marking Keep Current Value for most of the attributes.

    • For existing Functional Setups, if additional parameter was entered it wiped out previous settings.
    • Project File Includes and Excludes property can now be configured to control files populated on Project Files tab for EBS projects.

...

FlexDeploy 4.0.3 - Patch Release 05-05-2017

General/Usability

  • FDBLD_ENVIRONMENT_CODE and FDBLD_INSTANCE_CODE variables are available in Build and Deploy workflow context, so that deploy workflow can understand where Build was performed if necessary.

  • EnvironmentCode and InstanceCode variables are available in Version Syntax script now.

...

FlexDeploy 4.0.3 - Patch Release 04-24-2017

General/Usability

  • Improved error messages for ServiceNow integration.

  • Setup timeout on ServiceNow API calls to avoid stuck threads if ServiceNow instance is not responding in timely manner.

  • Deployments were getting stuck in Pending Approval mode, if there were more than one ServiceNow change tickets.

  • Links on Request and Execution screens have scroll bar now if there are many links for ServiceNow.

  • Updated Linux endpoint execution script to use Non-Bash safe syntax.

  • Added Re-Sort button to allow users to sort SQL objects after new files are populated from SCM. All new files are sorted but appended at the end in SQL Objects for EBS, so this would be helpful option.

  • Fixed issue – Maintain order on Re-build Package (Gear click).

...

FlexDeploy 4.0.3 - Patch Release 04-07-2017

General/Usability

  • ServiceNow integration improvements to support Change Requests and Service Catalog Requests.
  • Workflow designer variable lookup updated to show Perforce and ClearCase related project source variables.
  • Clone depth for Local git repository updated to 2000. This should help with SCM file revision lookup on build request screen.
  • Change Management System – Related Changes input was missing on Partial Deployments project deploy request form.
  • Added support for Partial Deployments project to mass load project templates.
  • For Build All files scenario tolerate if some files are not found, this can be the case if some files are not part of stream being built.
  • Added FD_WF_USER and FD_WF_USER_EMAIL to Workflow Execution Context.
  • Added FD_ALL_FILES_REQUESTED and FD_PACKAGE_NAME to Workflow Execution Context.
  • Project Explorer tree will remove empty folders when performing Filtering. This should allow users to find specific projects easily.
  • Minor fixes to Test Connection for various SCM Instances to handle unexpected exceptions and show better error messages.

...

These release notes provide a high-level summary of the changes between FlexDeploy 4.0.2 and 4.0.3, and describe any changes that impact existing implementations.

General/Usability

  • Integration with ServiceNow to link FlexDeploy approvals with change requests. User can provide Change Request when submitting deployment request. Configurations are also possible to auto create change requests during deployment, or incidents upon deployment failure.
  • New screen to view build/deploy request detail, including pending and scheduled tasks, and linked JIRA/ServiceNow tickets. This allows users to view request details even when execution has not started. Requester can also cancel request if desired. 
  • FlexFields can now be configured for build requests in addition to deploy requests. FlexFields values are now available in Workflow Execution Context. Build request related FlexFields values are made available during deployment request also.
  • Improvements to Partial Deployment model, providing hybrid approach to manage full and partial deployments in a single project. Users can easily submit build request for all project files. Continuous Integration can also be setup for Partial Deployment project where package will be built with all files when change is detected in SCM.
  • Security Realms (LDAP) now support Oracle Virtual Directory (OVD).
  • Reports improvements – additional search criteria and results columns.
  • Required FlexFields must be entered before saving on the Continuous Integration page.

...

  • Subversion
    • For Partial Deploy projects, tagProjectSources operation now only tags files included in package instead of all files.
    • tagProjectSources operation now supports tag prefix and suffix to support use cases for tagging within deploy workflows.
  • Microsoft TFVC
    • For Partial Deploy projects, labelProjectSources operation now only labels files included in the package instead of all files.
    • labelProjectSources operation now supports label prefix and suffix to support use cases for tagging within deploy workflows.
  • Perforce
    • Checkout and export operations now support use of Label, previously only Change List Id was supported.
    • Issue fixed where Plugin operations failed to delete client/workspace.
    • Local workspace location is now relative to the FD_TEMP_DIR. This affects an input in most of the operations. Because of the new changes, you should put only relative paths or leave the input blank.
    • Add and Delete operation inputs have changed significantly, please see the Plugin Guide.
  • APEX
    • For the deploy operation, if the APEX SQL Files cannot be found, the plugin will return an error instead of ignoring the missing file.
  • Oracle Service Bus
    • Improved performance of concurrent OSB build executions.
    • Updated classpath for 12.2.x to include missing XQuery libraries.
  • Oracle MFT
    • Operation and plugin names changed for consistancy. Plugin is now "Oracle MFT". The operations changed from Build to build and Deploy to deploy.  This name change will require updating the workflow to use the updated names and to re-associate the plugin operation to your instance to make properties available.
    • Added support project file object type of OTHER.  These are file types which are unrecognized, and not moved by default.
  • Oracle Database
    • Fix for renaming tables when they are referred to by triggers.

      Note
      titleUpgrade Note

      The FDDB schema was changed from 4.0.2 Please run the 4.0 to 4.0.3 schema changes before using the 4.0.3 plugin.


  • Oracle EBS 
    • Fix for a few SQL commands executed twice during deploy.
    • Fix for MDS target attribute issue with extra mds folder.
    • Fix for generateCustomJar operation output data type issue.
  • Oracle B2B
    • Added B2B_User input on the plugin to allow a specific user to be set on the import operations
    • Fix for property replacement in configuration files.
  • Oracle OBIEE
    • OBIEE partial builds can be performed from SCM as well now. See the plugin guide for more information.
  • WebLogic 
    • Fix for JMS System Module creation

...

  • FlexDeploy can now be installed on Apache Tomcat (version 8.55)

General/Usability

  • Override Project properties (Project or Environment-Instance scope) by combination of Environment, Instance or Environment/Instance. For example, you can now configure different WebLogic server name for each Environment.
  • Properties and Plugin inputs are now displayed using friendly display name, with "copy code to clipboard" icon for use in various Groovy scripts.
  • Workflow editor provides options to lookup variables/codes for use in Workflow Groovy scripts. 
  • View running/completed tests within dashboard.
  • Define security to control who can submit deployments to which environments.
  • Run workflows on an out-of-the-box endpoint (localhost) representing the FlexDeploy server.
  • Abort running workflows.
  • Stop deployment of dependent package(s) when executing deployment fails (partial deployment).
  • Type ahead search mechanism on build request form (partial deployment).
  • Multi-select to move project files to another type (partial deployment).
  • Multi-select to inactivate project files (partial deployment).
  • Multi-select to regenerate build/deploy commands (partial deployment).
  • Show new project files after populate (partial deployment).
  • Build package with changed files since last build (partial deployment).
  • Additional sample workflows provided.
  • Filtering of properties on Project and Environment Instance properties screen.
  • Requested By, Package Name and Project Version is now available as filter criteria on Project current activity table.
  • Project files filter button now works with press of Enter key. It also supports more complex filtering where you can type in multiple words separated by space and system will try to find best match files. 
  • Submit build or deployment request form will only list Environments that are mapped to project build or deployment Instance(s) respectively. 
  • Deployment submitter can now cancel associated Scheduled Task, even if they do not have Update permission to Scheduled Task. This is not true for Approval Tasks, which can only be cancelled by member of Group that has Approval Task.

...