Any one please help me to know answers for below questions?
Any one please help me to know the answers..
1.When we have write now why again explicit commit method is there?
2.In Which Case Editable data page will be useful?
3.In which scenarios we will use advance agent.Need few Scenarios ?
4.When declare expression execute automatically they why we have property seek method?
Accepted Solution
Pegasystems Inc.
IN
To answer your 4th query:
Property-Seek-Value method
Use this method to initiate backward chaining computations for the value of a property, based on Declare Expression rules.
For example, the standard activity Work-.VerifyProperty — referenced in the standard flow action Work-.VerifyProperty — calls this method.
Parameters
This method has four parameters:
To answer your 4th query:
Property-Seek-Value method
Use this method to initiate backward chaining computations for the value of a property, based on Declare Expression rules.
For example, the standard activity Work-.VerifyProperty — referenced in the standard flow action Work-.VerifyProperty — calls this method.
Parameters
This method has four parameters:
GoalProperty : Identify the property to compute. This must be the Target Property key part of a Declare Expression rule.
AlwaysRecompute : Select to force the system to compute the value of the property identified in the GoalProperty parameter even when the property already is present on the clipboard and has a non-null value. In most cases, leave this box cleared, so that the Compute Value field in the Declare Expression rule applies.
AlwaysForwardChain : Select to cause the system to forward chain after backward chaining, even when the goal-seek attempt failed. If not selected, when goal seeking fails, any property changes made by the goal seek process are not considered for forward chaining. In most cases, leave this box cleared.
MissingReference Property : Optional. Enter a target property, a local variable, or an activity parameter. When backward chaining fails to compute the property identified in the GoalProperty parameter, the method stores name of the property that prevented the computation from completing there.
Results :
This method uses backward chaining on the declarative network defined through Declare Expression rules to compute or recompute the value of the goal property.
The system uses the GoalProperty parameter and class of the step page (or primary page) as the Applies To key part to search for the Declare Expression rule. It then uses the Declare Expression rule to starts backward-chaining computations to obtain a value for the property.
If backward chaining is successful, the result is a new value for the property identified in the GoalProperty parameter. (Other properties may also have new values, all consistent with Declare Expression rules and other declarative rules).
If the backward chaining computation is unable to compute a value for the GoalProperty property, it may return instead the name of another property (identified in the third parameter) that — if it had a value — could contribute to the computation. Your application may then prompt a user for a value for this property, or use other means to obtain this value.
More on this : https://community.pega.com/sites/default/files/help_v721/procomhelpmain.htm
Hope this helps.
Best Regards,
Mounika
Pegasystems Inc.
IN
Hi,
To answer your 1st query :
- Write-Now doesn't change the transaction id, where as commit does .
- Usually prpc internal activities utilize a Write-Now (e.g. in the case of a failed commit)
- Use the Obj-Save method with the WriteNow option primarily outside of flow processing. Here are some examples of when to use Obj-Save with the WriteNow option selected:
a) In a rule called by a SOAP service, you might save one object with the WriteNow option selected because it is unnecessary to perform a deferred transaction (Obj-Save or Obj-Delete) for one object that is immediately followed by a Commit transaction.
b) Write to a log to report progress during a transaction.
- When deciding whether to select the WriteNow option in the Obj-Save method, consider the following ramifications:
The Obj-Save WriteNow transaction can be overwritten by a previous deferred Save.
The Obj-Save WriteNow transaction prevents rollback when there are errors.
The Obj-Save WriteNow transaction does not represent the end of a transaction in and of itself.
The Obj-Save WriteNow transaction does not release a lock or terminate other deferred saves if the Obj-Save WriteNow transaction fails.
Pegasystems Inc.
IN
Hello Srinivas,
Regarding the query: 1.When we have write now why again explicit commit method is there?
To add to Haritha, please check:
https://community.pega.com/sites/default/files/help_v722/procomhelpmain.htm
https://community.pega.com/sites/default/files/help_v722/procomhelpmain.htm
Best Regards,
Mounika
Pegasystems Inc.
IN
To answer your query: 2.In Which Case Editable data page will be useful?
Editable — Provides the initial contents of a page that can be accessed in normal read-write mode.
- Editable data pages do not have a refresh strategy and cannot be node-level in scope.
- Editable data pages are displayed in the User Page list on the clipboard
An editable page loads only once upon first reference and continues to use the same data upon subsequent references. This allows us to modify the page without worrying about overwriting the data. While data pages can be editable they do not automatically persist back to the source. That must be done explicitly."
Another difference between editable and read-only pages is "Editable pages" are displayed under user pages where as the "read only pages" are found under Data pages in the clipboard.
Hope this answers that query.
Best Regards,
Mounika
Pegasystems Inc.
IN
Hi,
To answer the 2nd query :
As the name says, editable datapages,allows the datapage to be modified
usecase :
1) if you want to populate a repeat grid, whose source is a pagelist, and inturn pagelist refers to a readonly datapage . And if you want to set the repeat grid to inline mode(i.e you want to edit a row)
In this case, system throws the error saying
"The page or property D_xxxx.pxResults is read-only, and cannot be modified."
This scenario works only if you modify the datapage to editable .
Note : Also note that, editable pages are passivated, but readonly pages are not.
Pegasystems Inc.
IN
To answer your 4th query :
property-seek-value method helps to compute the value of a property based on declare expression rules(prpc allows a computation to advance even when the value of an input or parameter property is not available)
See if this helps :
https://community.pega.com/sites/default/files/help_v717/procomhelpmain.htm
Incessant Technologies
GB
For your 3rd query ...we use an advanced agent when we dont need any queueing.
example: you need to close all the cases of particular case type which are having a particular status .Here the advanced agent automatically checks the list of cases and close those cases which are having a particular status.There are many more scenarios which uses advanced agent.
Regards,
Srijith.
Coforge
IN
Thanks for reply Srijith.
Looks like the above scenario is one time only. if yes then the same we can do using activity by doing obj browse and obj save. why for advance agent?
Pegasystems Inc.
IN
Hi,
As said : The advanced agent is doesn't use any agent queue functionality. The agent just wakes up at the specified timeinterval , runs its activity and sleeps.
eg : If you want to run a report (reportdefinition), daily at 10:00AM and send them to users, you can use the advanced agent.
It doesn't require any queue item to be created.
Accepted Solution
Pegasystems Inc.
IN
To answer your 4th query:
Property-Seek-Value method
Use this method to initiate backward chaining computations for the value of a property, based on Declare Expression rules.
For example, the standard activity Work-.VerifyProperty — referenced in the standard flow action Work-.VerifyProperty — calls this method.
Parameters
This method has four parameters:
To answer your 4th query:
Property-Seek-Value method
Use this method to initiate backward chaining computations for the value of a property, based on Declare Expression rules.
For example, the standard activity Work-.VerifyProperty — referenced in the standard flow action Work-.VerifyProperty — calls this method.
Parameters
This method has four parameters:
GoalProperty : Identify the property to compute. This must be the Target Property key part of a Declare Expression rule.
AlwaysRecompute : Select to force the system to compute the value of the property identified in the GoalProperty parameter even when the property already is present on the clipboard and has a non-null value. In most cases, leave this box cleared, so that the Compute Value field in the Declare Expression rule applies.
AlwaysForwardChain : Select to cause the system to forward chain after backward chaining, even when the goal-seek attempt failed. If not selected, when goal seeking fails, any property changes made by the goal seek process are not considered for forward chaining. In most cases, leave this box cleared.
MissingReference Property : Optional. Enter a target property, a local variable, or an activity parameter. When backward chaining fails to compute the property identified in the GoalProperty parameter, the method stores name of the property that prevented the computation from completing there.
Results :
This method uses backward chaining on the declarative network defined through Declare Expression rules to compute or recompute the value of the goal property.
The system uses the GoalProperty parameter and class of the step page (or primary page) as the Applies To key part to search for the Declare Expression rule. It then uses the Declare Expression rule to starts backward-chaining computations to obtain a value for the property.
If backward chaining is successful, the result is a new value for the property identified in the GoalProperty parameter. (Other properties may also have new values, all consistent with Declare Expression rules and other declarative rules).
If the backward chaining computation is unable to compute a value for the GoalProperty property, it may return instead the name of another property (identified in the third parameter) that — if it had a value — could contribute to the computation. Your application may then prompt a user for a value for this property, or use other means to obtain this value.
More on this : https://community.pega.com/sites/default/files/help_v721/procomhelpmain.htm
Hope this helps.
Best Regards,
Mounika