User Form Activity on a Xanadu PID: not working properly?

[Hangmanmio]

Hi @Lisa Holenstein, all,  

I have come across an issue with Playbooks OOTB activities on the Xanadu PDI (but similar issue was reported by colleagues, working on a customer dev instance and another PDI on Washington): OOTB User Form activity does not "behave" the same way as in older ServiceNow: the automation behind this activity is Manual Activity flow instead of User Form Activity flow, check this out: 

Hence, the Input fields allowed are only Assignment Group and Assigned To. This issue (feature?) severely limits the functionality of this Playbook activity (before, User Form activity allowed very versatile input and was quite useful OOTB activity). Also, there are 2 Activity Definitions with the same name (User Form):

The inactive one is the one with the correct (in my opinion) flow; unfortunately, you cannot activate it: 

The workaround my colleagues and I used was to create a custom activity definition with the same Automation Plan and Activity Experience as the inactive Activity Definition. 

However, I wonder whether that was an intentional change in the OOTB functionality in the recent releases or just a bug? Is there another way to activate this activity definition (that I am missing)? 

Thank you in advance!

Regards,

Mia

[Lisa Holenstein]

Hi Mia,

I checked this activity and the underlying subflow on a Washington Patch 8 and Xanadu Patch 2 instance. The active activity definition that you see on your PDI (c9839e38b701311004c164fdde11a904) is the same on both instances with the same "Manual Activity" subflow (cb18ceef1b230010affd0e55cc4bcbf2). The only thing I can see that's different, is that we added the "Restart" activity action to the activity definition. This should not lead to any different execution.

I'm not sure where the other, inactive activity definition comes from, but I don't see any reason for User Form to behave any different on the Xanadu instance than previously. If you still see deviating behavior on your instance, please try and update or repair the store apps for Workflow Studio and Playbook Experience from the Application Manager. If this does not solve the issue, please submit a case through the Support portal.