Question
IP Australia
AU
Last activity: 6 Apr 2016 21:38 EDT
Why cant we use pyWorkPage Hard Coded when we are building framework?
Why cant we use pyWorkPage Hard Coded when we are building framework?
Message was edited by: Lochan to add Category
Accepted Solution
Infosys
AU
It is a best practice not to hard code pyWorkPage in rules, but as such it is not restricted to use pyWorkPage hard coded in frameworks.
Few scenarios I can think of are:
- When agents process a WO, work page might have been loaded by agents into a named clipboard page having a different name other than pyWorkPage.
- If there is a cover concept, same WO might be a cover case (pyWorkCover) in one scenario and might be a child/actual case (pyWorkPage).
- Might want to reuse a rule (say data transform) when primary page is pyWorkPage and also when primary page is different from pyWorkPage.
Murali...
Accenture
IN
As per my understanding, while we are building framework it should be more generic. If we use pyWorkPage, at runtime, there will be some scenarios where WorkPage will not be pyWorkPage and if Implementation Work inherited from framework Work-, then it will create issue. So it will be always better to get the Work Page as Parameter in the Framework activities
Accepted Solution
Infosys
AU
It is a best practice not to hard code pyWorkPage in rules, but as such it is not restricted to use pyWorkPage hard coded in frameworks.
Few scenarios I can think of are:
- When agents process a WO, work page might have been loaded by agents into a named clipboard page having a different name other than pyWorkPage.
- If there is a cover concept, same WO might be a cover case (pyWorkCover) in one scenario and might be a child/actual case (pyWorkPage).
- Might want to reuse a rule (say data transform) when primary page is pyWorkPage and also when primary page is different from pyWorkPage.
Murali...