Create a Catalog Task, then add Catalog Item Variables#87
Create a Catalog Task, then add Catalog Item Variables#87SapphicFire merged 4 commits intoServiceNowDevProgram:mainfrom
Conversation
|
🚫 Unexpected files changed in PR Thank you for your contribution. However, it seems that the file changes in this Pull Request are incorrect or invalid. Allowed patterns: Closing this for now. Once you make additional changes, feel free to re-open this Pull Request or create a new one. If you feel that this PR should be accepted in its current state, please reach out to Astrid Sapphire (SapphicFire) on GitHub, or in the SNDevs Slack Hacktoberfest channel. |
|
Reopening while I look into what is happening |
|
🚫 Unexpected files changed in PR Thank you for your contribution. However, it seems that the file changes in this Pull Request are incorrect or invalid. Allowed patterns: Closing this for now. Once you make additional changes, feel free to re-open this Pull Request or create a new one. If you feel that this PR should be accepted in its current state, please reach out to Astrid Sapphire (SapphicFire) on GitHub, or in the SNDevs Slack Hacktoberfest channel. |
|
Ok! So I've figured out what happened. The workflow could not trace back to a shared base commit for merging, and so when comparing it believed that you had deleted 28 files in this PR. |
SapphicFire
left a comment
There was a problem hiding this comment.
Looks good to me. I can tidy up the duplicate action in a future PR
This action is useful in Flows/Subflows that are used with more than one Catalog Item, and/or Catalog Builder items that don't yet exist. You can pass in values for the Catalog Task Short Description, Description, and Assignment group, or it will use the values of Catalog Item variables named v_catalog_task_short_description, v_catalog_task_description, and v_catalog_task_assignment_group. A script then adds all of the Catalog Item variables to the task. In this way, the variable names to not need to be known, or even exist when the flow is created as it will add all of the variables that exist when the action is executed. In the flow/subflow after calling this action, you may want to add a Wait for Condition activity to wait until the Catalog Task record (the data pill from the Action) Active field = false.