Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Application Release Automation1.81

Use > Automate Release > Release pipeline > Release gate actions

Release gate actions

Codar allows you to configure release gate actions at each lifecycle stage. These actions act as a gate between two lifecycle stages. A package has to pass through each action that is defined; hence they are called release gate actions. During promotion of the package, the gate actions defined in each are executed. After all the actions complete successfully, the package transitions to the next lifecycle stage.

You can configure the following release gate actions:

Deploy Application - this action deploys the Codar application design on the specified target environment. If the design is a partial design, the micro service designs that meet the requirements of the application design must also be selected.
Run OO Flow - this action executes the specified flow in Operations Orchestration. Typically this action can be used to execute specific tests, with or without a deployment instance.
Add Approver - this action is used to configure approvers who will approve the package promotion. It is also used to configure the minimum number of approvals, automatic approvals, and the number of days after which the automatic approval process is triggered.
Execute Test Set - this action can be used for executing specific tests with or without a deployment instance.
Run Script - this action can be used to execute a script on a remote machine, with or without a deployment instance.
Consume CMP Service - this action can be used to execute cloud offerings from CSA. After an offering is realized, the same can be used to deploy applications.

Note: You need permission to configure release gate actions.

Deploy Design action versus Run OO Flow action

Deploy Design actions are typically created to test your environment and to perform a test deployment before promoting your design to the production stage.

Run OO Flow actions are typically used to execute operations or tests on a deployed instance. You can also execute these actions without an instance of a deployment.

Disable or Enable a release gate action

Any action you create will be in enabled state by default. You can disable or enable a disabled release gate action during any stage in a lifecycle.

To disable or enable a release gate action

Navigate to Release Automation > Release Pipeline.
Select the design type (Topology Designs or Sequenced Designs) from the drop-down list.
Select the application and the version which contains the release gate action you want to disable or enable.
Click the gear icon next to the lifecycle stage which contains the release gate action you want to disable or enable and click Configure Gate Actions. The Configure Gate Actions for <lifecycle stage dialog appears, listing the available release gate actions.
Use the Enable or Disable link appearing against the respective release gate action to enable or disable the same.

Note You cannot disable or enable release gate actions, if there is a dependency among the release gate actions being disabled/enabled .

Similarly, you cannot rearrange the order of execution of release gates in case there is a dependency among the release gates being rearranged.

For example, if output properties of Release Gate action 'A' have been used in Release Gate Action 'B', then you cannot rearrange action 'B' to be executed before action 'A'.

Send Help Center feedback