Solutions

RLC: Passing parameters to task, using "Customer Task Validation Rules", using "Custom DU Validation Rules", creating custom code to be passed



ID:    S143484
Published:    09 July 2021
Updated:    09 July 2021

Operating System(s)

  • All Windows

Product(s)

  • Release Control
 

Description

Beginning in RLC 6.2.3, you can pass information about the Release Package to the tasks. You can pass this information to any task that allows parameters. 

 

In this document, we will walk through:

  • How to pass information about the Release Package to a task.
  • How to setup "Custom Task Validation Rules" to ensure users are passing the correct values to the task.
  • How to setup "Custom DU Validation Rules" to ensure that required tasks are always included
  • How to create custom code to pass in parameters (added in RLC 6.2.6)

 

By default, the following code options can be passed to a task:

  • ${ISSUEID}    Release Package ID number
  • ${TITLE}       Title of the Release Package
  • ${URL}        Full URL to open the Release Package

 

The example use case in the attached document uses Manaul Tasks. After a manual task is created, it is hard to understand which Release Package the task belongs to. In this example, we use the features above to creat a 2-way link between the Release Package and Manaul Task and back to the Release Package.  This is only one example. The same feature can be used with any Task that allows parameters.

 

UPDATE: The built-in feature to pass code to an RLC Task using a Parameter only allows you to pass ${ISSUEID}, ${TITLE}, and ${URL}. If you want to add additional code options, follow the steps in the attached guide.

 

Resolution

Details and screen prints are in the attached document. At a high level, the steps go like this:

 

Creating 2-way Link with Release Package and Manual Task

  1. Create a listing report that will query for the linked Release Package by ISSUEID number.
  2. Update the Manual Task process app to accept the new parameter and display the value on the forms.
  3. Update the Manual Task plugin configuration to allow for the new parameter.
  4. Setup a validation check in the RLC Custom Task Validation Rules AUX table.
  5. Update the Release Packages to use the new rule by default.

Passing Parameters to a Deployment Automation Task

  1. Setup DA’s process to accept a parameter for the Release Package information. (No special plugin configuration is required.)
  2. Setup a validation check in the RLC Custom Task Validation Rules AUX table.
  3. Update the Release Packages to use the new rule by default.

Passing Parameters to a  ZMF Task

For ZMF, the steps are slightly different because more than one ZMF Package could be deployed at the same time. Also, ZMF does not allow for parameters during a deploy. Instead, the user will need to include an “update properties” task for each ZMF Package that is being deployed. This means we need two validations. The first is a “DU Validation” to make sure that each ZMF Package will be updated. The second is a “Task Validation” (like above) to make sure the “update properties” task has the correct code in it.  For ZMF the basic steps are:

  1. Make sure the ZMF Packages have a parameter for the Release Package information.
  2. Setup an “RLC Customer DU Validation Rule”. This rule tells the system that every DU (ZMF Package) must have a matching “update properties” task.
  3. Setup a Deployment Task Rule to validate if the information in the “update properties” task is correct.
  4. Update the Release Packages to use the new rule by default.

 

Attachment

File NameFile SizeDownLoad
Creating 2-Way Link With Release Package.docx 589K HTTP
Creating a Custom RLC Code for Use with RLC Task Parameters.docx 202K HTTP

Rate this Solution

Find Answers

Type a question or describe what you are looking for below

My Recent Searches

Welcome kb sso

Additional Assistance

  • Submit a Case Online
  • FAQs