Headless/Straight Through Processing and SLA's
Hi all,
I am just starting to look at implementing a "headless" or "straight-through process", which involves receiving updates from an external web service throughout the life of a record in an external database. Basically something like this
System 1
- Creates record
- Edits and either rejects the record (ending the overall process) or passes it on to the next step
System 2
- Receives the record and processes it in a batch job
- Edits and either rejects the record (ending the overall process, as above), or passes it on to the next step
System 3
- Receives the record and processes it
- Modifies certain key fields such as status, some dates, etc.
System 4
- Receives the record and processes it
- Finalizes the record (end of the overall process)
My question is around how to apply SLA's to each of these steps (i.e. the part where each external system handles the record). Since I have no assignments to make (no actual user interaction to update the record), where can I define an SLA? I am a little bit lost on this, my basic idea is to have a stage for each external system's process, and a step for each of the couple of things that the system can do. Each update would cause my Pega process to note that update.
What we are trying to do is provide overall visibility to the life of this record, and do metrics on how many stay in System 2 for longer than a certain period of time, that kind of thing.
Hi all,
I am just starting to look at implementing a "headless" or "straight-through process", which involves receiving updates from an external web service throughout the life of a record in an external database. Basically something like this
System 1
- Creates record
- Edits and either rejects the record (ending the overall process) or passes it on to the next step
System 2
- Receives the record and processes it in a batch job
- Edits and either rejects the record (ending the overall process, as above), or passes it on to the next step
System 3
- Receives the record and processes it
- Modifies certain key fields such as status, some dates, etc.
System 4
- Receives the record and processes it
- Finalizes the record (end of the overall process)
My question is around how to apply SLA's to each of these steps (i.e. the part where each external system handles the record). Since I have no assignments to make (no actual user interaction to update the record), where can I define an SLA? I am a little bit lost on this, my basic idea is to have a stage for each external system's process, and a step for each of the couple of things that the system can do. Each update would cause my Pega process to note that update.
What we are trying to do is provide overall visibility to the life of this record, and do metrics on how many stay in System 2 for longer than a certain period of time, that kind of thing.
Any tips to help me get started? I am not asking for you guys to write my system for me just looking for how to approach this thing.
Thanks again!
Pegasystems Inc.
IN
If you are planning to use Stages for each system's process, you might want to consider defining SLAs at Stage level. Which PRPC version are you using ?
Pegasystems Inc.
FR
Hi Jim,
As requested by Pankaj, your PRPC version might be interesting to have in order to fully appreciate which options are available to you. Now having said that, regardless of the version you can surely create a ghost assignment with an SLA in it pending the external system to resume the original assignment and of course to resume that ghost assignment as well.
I'm saying ghost because you can assign it to a WorkBasket invisible for your users. Just to be used by the system.
