Question
Morgan Stanley
US
Last activity: 1 Jun 2021 10:31 EDT
Case creation via Job scheduler, taking a default prefix- then set on application
Case creation via Job scheduler, taking a default prefix- then set on application
New job scheduler to create case configured to run on S.R.C Updated S.R.C with implementation application Still while creating case, prefix- defaulting to "C-"
Pegasystems Inc.
US
Hi @SasidharB9516,
I'm not sure I follow. Do you need help with something?
Morgan Stanley
US
Though there is prefix- mentioned on application for case type, when created case via job scheduler creating case with default prefix- "C-" why?
Steps
1.New job scheduler to create case configured to run on S.R.C
2.Updated S.R.C with implementation application
Issue - Still while creating case, prefix- defaulting to "C-"
Pegasystems Inc.
FR
You might have a MODEL firing somewhere and changing the prefix unexpectidely. Can you trace it and check?
Infosys Limited
IN
You might have used a standard agent/ Process Queue for the case creation within the Job Scheduler. In the calling activity, please check if the privileges have been removed, and is checked for direct invocation.
Cognitonic Systems Australia
AU
@SasidharB9516In general it should take from case type rule. Whenever case is created pyDefault at case level will be triggered. When this happens pyDefault DT which is in @baseclass is also triggered as "Call superclass data transform" is checked by default. In this .pyWorkIDPrefix is initialized with "C-" as prefix. If work object prefix is not overridden either in pyDefault DT at the case level or not considered from Case Type rule then this prefix is set when while creating case.
Can you try any of below methods.
1. Update JS context to Specify Access Group and mention your application access group. If still this doesn't work try second approach.
2. Create one pyDefault DT in the Case Type Class and initialize this property with corresponding Prefix and specify the context as System Run Time Context.