Set Assignment Group for Specific Tasks within the Child Playbook

[AfrozaHassan001]

Hi All!!
For playbook there's a lane under which I have a few activates/tasks. For a few tasks I want the to set the assignment group to something else. My approach is to go directly to the specific activity definition and set the assignment group there as shown in the screenshot attached. (For SS I have left it blank), but it's not working. The activity is picking up the assignment group which I assign to the case on creation of it. 

Please help me out as to what other approach I can follow to achieve it. 

[Daniel_san]

Dear @Drushika 
I believe this is a version-related bug: the same issue started happening to us after upgrading from Yokohama to Zurich.

As a workaround, you can set the group without any problem from the Classic UI by locating the activity in the sys_pd_activity table. After filled the "Assignment group" field in the classic UI, reload the playbook in the Workflow Studio page and the field should appear correctly populated in the Activity settings.

[Drushika]

That's really a good workaround. Thank you @Daniel_san. 

[Drushika]

@Daniel_san  -  Question entered on the Questionnaire activity is not saving correctly and showing as the question_sys_id in the preview activity, Did you by any chance noticed this issue as well ?

[Daniel_san]

@Drushika: We haven’t experienced what you’re describing… I can’t help, I’m sorry.

I would recommend trying to update the components/apps related to Workflow Studio... and/or directly opening a case with the vendor. In my opinion, as in the previous case, it would clearly be a bug, but this time, if you want the questions to display correctly (I’d like to think that even if they look wrong in the preview, they appear correctly in the TASKS), there’s no workaround.

[yaronguez]

Changes made to an activity definition's automation inputs or experience properties do not impact any  instances of that activity definition within a Playbook. You can think of an activity definition as a template for adding activities to your Playbook. Once the activity is added, you have to update the activity itself and not the definition in order make changes. The recommended way to do this is through the activity side panel within Workflow Studio so that it will honor all validation rules. However, you can technically edit the activity directly throuhg UI16 in the sys_pd_activity table as described above. Just note that any changes made directly to the activity record will not go live until the Playbook is re-activated within Workflow Studio.

Note, the following changes to an activity definition will impact existing instances of that activity within Playbooks:

1. Its Automation (sub-flow, flow or flow action), e.g. changing "Wait for Condition" to "Update Record".
2. Its UI Layout, e.g changing "Record" to "List".
3. Its Declarative Actions Mappings including adding, removing, or re-ordering any of its Declarative Actions.
4. The Declarative Actions themselves, e.g. changing the server script of an "Update" button.
5. Its Activity UI, e.g. adding an image to a List UI.

We have plans to simplify this in the future to avoid making unintended changes to any existing Playbooks from outside Workflow Studio. 

As for the question_sys_id issue, that definitely sounds like a bug that I haven't seen before. Please work with support to open a case and we can look into it for you.

Cheers!

Yaron