Task Properties

The following table describes the properties that are common for all the tasks.

Item Purpose Mandatory/Optional
Name Enter a suitable name that describes the task clearly. Mandatory
Make Task Mandatory Check this box for tasks that you want the program participants to execute mandatorily. Optional
Description Describe the purpose of the task and provide clear instructions so that the enrolled partners understand what they are supposed to do and why. Optional
Dependencies Determine whether to make this task mandatory, the order in which the tasks are to be performed, dependencies on one, more, or all of the tasks that come before this task.  
To Be Executed By

Select a group of users or an individual user for whom the task is intended. The following options are available:

  • Partners: This option mandates the task to be performed by all partners.
  • Any Internal User: This option allows any user from the program owner organization to perform this task for each enrolled partner.
  • Select Internal Users: This option allows you to select specific users from your organization to perform the task for each enrolled member.
 Mandatory (Default is Partners)
Internal Reviewer

Select if you want the task to be internally reviewed after the execution. The following options are available:

  • None: An internal review is not required.
  • Partners: This option allows all the partners to review the task before marking the task completed.
  • Any Internal User: This option allows any user from the program owner organization to review the task execution and then accept or reject it.
  • Select Internal Users: This option allows you to select specific users from the program owner organization to review the task execution and then accept or reject it.
Mandatory (Default is None)
Post Execution

Success/Failure Messages: Enter messages (successful and failure) that will be displayed once the task is fully executed. Message size is limited to 255 characters.

Note In the Onboarding and Testing Cloud 21.6 release, failure messages are applicable only for the API Collection task and can be added for each API.

Environment variables: These variables can be used to share required values with other tasks. Values for the configured variables get updated only after the task is completed, irrespective of the passed or failed executions. Once the variables are set, they are available to all the tasks within the same program at the execution level.

 Optional

The following table defines the properties specific to the Agreement task.

Name Description Usage
Agreement Upload the documents that you want your trading partner to agree to, such as Terms and Conditions, Non-Disclosure Agreement, Service Level Agreement, and so on. Mandatory
Consent Text Enter the text that you would like your partners to consent with. The default text is I Agree. Mandatory
Signatories Specify the role of the signatory who must sign the agreement on behalf of the partner organization. Mandatory

The following table defines the properties specific to the Data Collection task.

Name Description Usage
Reference Documents Upload the reference documents to clarify what type of information you expect to receive from your partner and help them provide that information in the correct format. Optional
Data Collection Form JSON Configure the business form using JSON schema so that partners can enter the data or upload the documents. Optional

The following table defines the properties specific to the Share Information task.

Name Description Usage
File Upload the files or documents that you want to share with the program participants, such as companion guides, business rules, and so on. Optional

The following table defines the properties specific to the Testing task.

Name Description Usage
Add Step Configure the testing conditions to ensure that the tasks are executed correctly as a one-step or multi-step process. Optional

The following table defines the properties specific to the Certificate task.

Name Description Usage
Organization Seal Upload an image of your organization seal. Optional
Organization logo Upload an image of your organization logo. Optional
Certificate Title Select a name for the certificate for successful program completion to be issued to the program participants. Mandatory
Certificate Description Describe what the certificate stands for. Optional
Certified By Enter the name of the organization that issues the certificate. Optional
Validity in Days Provide the number of days for which this certificate is valid. You can leave this field blank for a perpetual certificate. Optional
Certificate Key for Authentication Choose None for no authentication key or System Generated for a system-generated authentication key that will be shared with the partner. The partner then has to enter that key on a specified URL to verify the identity and get the certificate authenticated. Authentication increases security and ensures that only a valid certificate goes to the intended party. Optional
Authentication URL This is a read-only field visible only when the user selects System Generated Value. This field displays the URL to visit to authenticate the certificate. Optional
Signatory Enter the name and designation of the person authorizing the certificate. You can include a maximum of two signatories. Optional

The following table defines the properties specific to the API Collection task.

Name Description Usage
Add API Add and configure APIs to be executed by either a partner or the program owner's organization. For more information, see Manage APIs in a Task. Mandatory

The following table defines the properties specific to the Branching task.

Name Description Usage
Question As a health plan administrator, frame the question for your partners. Mandatory
Answer Choices As a partner, enter answer choices (from 2 to 10 answer choices) for a question. Mandatory
Remarks for an answer choice Enter remarks or comments for your answer choice. Optional
Applicable tasks

For each answer choice, as a partner, select the tasks that are applicable for that specific answer choice. Each task can be:

  • Applicable: a part of the branching workflow.
  • Not Applicable: not a part of the branching workflow.
  • No Impact: not a part of the branching workflow, but visible to a participant. By default, all the tasks are marked as No Impact.)
 Mandatory

The following table defines the properties specific to the Validation task.

Name Description Usage
Max Execution Runs As a health plan administrator, restrict your partner to not create more than permissible execution runs. Mandatory
Validate Transactions Upload artifacts, such as guideline/severity/parser schemas for a specific task or select if the validation is performed using the trade relationships (processing rules) configured in Trading Partner Management. Note that in this case, only test environment trade relationships will be picked up for the validation of the partner transactions. Mandatory