@@Qtometa ok but how it will help here like when you don't provide the page name for obj-delete how it can delete the specific instance through refresh and lock could you please clarify this???
I am not sure about your question but to delete any instances, you need to make sure you have the lock. Lock can be acquired using multiple ways like while doing obj-open or by other method like obj-lock or obj-refresh-lock. If instances is already there we need page to delete instances, else you need to pass pzinskey key to delete using obj-delete-byhandle.
Through the work basket Two cases is transfer to Manager and senior manager but manager access only one case senior manager access both cases how do this scenario how to restrict manager can not access the second case on this work basket
Hi I fail to understand why would you not use savable data pages, or data pages that pega created when you make data type. None of this needed. Three data pages are generated automatically one for lookup, one for list and one for saving. Maybe I am missing something.
Once you start using in real, you will realize that list data page has default report definition and we can’t update that(if we do, data type view will get impacted), so in that case again we have to create a new RD. Look-Up we can use as it but also only for data, for case type we need only one in work layer to provide re-usability, Pega creates in each case type that we can simply delete and use work one.
Hi, could u make a small video for "Top" as page and "$Any" as class and then place holder rules like call the rule from run time context with example Thanks
Hi, What is the key benefit of refresh and lock ???
to make sure you have the lock, if not it will try to acquire.
@@Qtometa ok but how it will help here like when you don't provide the page name for obj-delete how it can delete the specific instance through refresh and lock could you please clarify this???
I am not sure about your question but to delete any instances, you need to make sure you have the lock. Lock can be acquired using multiple ways like while doing obj-open or by other method like obj-lock or obj-refresh-lock. If instances is already there we need page to delete instances, else you need to pass pzinskey key to delete using obj-delete-byhandle.
Through the work basket Two cases is transfer to Manager and senior manager but manager access only one case senior manager access both cases how do this scenario how to restrict manager can not access the second case on this work basket
This can be handled through skill and rating.
Thankyou sir
Hi
I fail to understand why would you not use savable data pages, or data pages that pega created when you make data type. None of this needed.
Three data pages are generated automatically one for lookup, one for list and one for saving.
Maybe I am missing something.
Save-able data page is an option, but that is still not much flexible and can’t be used in all scenarios.
Once you start using in real, you will realize that list data page has default report definition and we can’t update that(if we do, data type view will get impacted), so in that case again we have to create a new RD. Look-Up we can use as it but also only for data, for case type we need only one in work layer to provide re-usability, Pega creates in each case type that we can simply delete and use work one.
Hi, could u make a small video for "Top" as page and "$Any" as class and then place holder rules like call the rule from run time context with example
Thanks
Sure…