Cannot save the implementation layer case designs due to not being able to display the User Reference Field
I cannot save the implementation layer case design that I imported from the framework layer. There is a User Reference Field in the data class of a framework layer. The field is displayed in the approval routing to Specific User in the framework layer. However, the user reference field is not displayed in the implementation layer and could not be slelected from the dropdownn for the routing. In one hand routing is affected, and on the other hand, no other changes are saved as it requires to supply the user reference field before proceeding with any chanegs in the case designer of implementation layer.
What is causing this issue and what could resolve this issue of routing to User Reference Field and being able to save the case designer?
Accepted Solution
Pegasystems Inc.
IN
Hmm.. I think we might need to take help of a page here.
Since the User Reference Field in the data class of a framework layer its probably a good idea to refer it with help of a page.
So, instead of using it directly it in the section try using it like PageName.PropertyName and make sure you make the page available at runtime.
Share your result on this.
Hawaii Medical Service Association
US
Hi Santanu,
I get following error message:
"A valid user reference field must be selected or alternative routing should be configured."
However, the system does not provide me an ability to select the user reference in implementation layer case designer which is imported from FW layer case type and the FW case type has a user reference field. The underlying cause is that the user reference field created and selected in the FW layer is not being imported into the implementation layer. If I try to select the user reference field in the implementation layer, nothing shows up as if it is not defined but the same has been defined and used in the FW layer. Any thoughts, please?
Accepted Solution
Pegasystems Inc.
IN
Hmm.. I think we might need to take help of a page here.
Since the User Reference Field in the data class of a framework layer its probably a good idea to refer it with help of a page.
So, instead of using it directly it in the section try using it like PageName.PropertyName and make sure you make the page available at runtime.
Share your result on this.
Hawaii Medical Service Association
US
Hi Santanu,
I found the routing is working as expected without being the user reference field being copied to implementation case designer, I used an work around to save the case designer by changing from user reference field to username.