SBL-BPR-00236: A Workflow Monitor Definition Level was not found.

Applies to:

Product Release: V7 (Enterprise)


Version: 7.7.2.1 [18353] Fin Svcs


Database: Oracle 9.2.0.6


Application Server OS: IBM AIX 5L 5.2


Database Server OS: IBM AIX 5L 5.2





This document was previously published as Siebel SR 38-1934852152.


Symptoms

Hi there,





We have deployed the New Call Report Workflow to enable to toolbar icon to be used when creating a new call report.





In order to monitor any failures, we have set the Monitoring Level to ‘4 – Debug’ on the Admin – Business Process > Workflow Deployment view. This works fine when connected to the server client. However, after extracting a new local db and initiating a new call report using the toolbar button from the local client, the following error is displayed.





“A Workflow Monitor Definition Level was not found.(SBL-BPR-00236)”





After clicking OK to the error, nothing happens so users are unable to create call reports using the New Call Report workflow.





After setting the Monitoring Level back to ‘0 – None’ locally, the error no longer appears and the call report is created successfully.





I tested this further and noticed that the error appeared for all the Monitoring Level values except ‘0 – None’. Perhaps the monitoring level values are not synchronised locally.





Please advise if we have missed something?





Please note, this error is only raised when connected to the local client.





Many Thanks,





Pratiksh


Solution

Message 1

For the benefit of other readers:.





Customer used Siebel Tools connected to server database to deploy a workflow process.


Then, customer used Siebel client connected to same server database to activate the workflow process and set the following:





a. Monitoring Level > 0, eg. set to '1 - Status' from the picklist.


b. Replication = 'All'





When activating a workflow process with the Siebel client, a record is created in the Administration - Business Process screen > Workflow Instance Monitor view, (S_WFA_DEFN_LOG table).





Next, customer extracted a local database for a mobile user which has visibility to the views in the Administration - Business Process screen.





When the mobile user initiated the workflow on the local database with a button click, an error message was raised to the client UI:





"A Workflow Monitor Definition Level was not found.(SBL-BPR-00236)"





The cause of the above error message in this situation is two folds:





1. Upon further investigation in the client-side log file, the workflow process was looking for a row in the S_WFA_DEFN_LOG for the executing workflow.





a. When no rows exist in S_WFA_DEFN_LOG for the workflow and the workflow's Monitoring Level > 0, the error message is raised.








[1/4]


Message 2

[2/4]








b. When no rows exist in S_WFA_DEFN_LOG for the workflow and the workflow's Monitoring Level = 0, the error message is not raised. This is because the Workflow Engine didn't have to log any step or execution information.





c. If the mobile user deleted the active version of the workflow, then activated the workflow process against the local database, the S_WFA_DEFN_LOG record is created. Afterwards, setting Monitoring Level to any value will work.





The missing row in S_WFA_DEFN_LOG when Monitoring Level > 0 caused the error message.








2. The customer's newly extracted local database was missing the row in S_WFA_DEFN_LOG for the executing workflow.





The record gets created in the Workflow Instance Monitor view when doing the following:





a. If you use Tools to deploy the workflow, and then activate the workflow, the monitor instance record is automatically created.





b. If you use Siebel client to import the wrokflow xml file to the active workflow process applet, this again also automatically creates the monitor instance record.





Both the above used the Object Layer configuration.





c. During the local database extract for the mobile user, the records from the Workflow Instance Monitor view were not routed.





The data from the S_WFA_DEFN_LOG table should be routed to the mobile client, to support mobile users running the workflow process against the local db with the routed active workflow process using Monitoring Level > 0.





....


Message 3

[3/4]








This behavior with S_WFA_DEFN_LOG data not being routed to local databases has been logged as a product defect:





CR # 10495935 : Mobile client: "A Workflow Monitor Definition Level was not found.", when no data in S_WFA_DEFN_LOG





At the moment, it is not possible to set up routing rules to route the data from this table to the local database. In order to do so, there needs to be additional columns added to this table to support the routing rules, and C++ code to set the columns to the appropriate values.





As a possible workaround:





If the number of mobile users and workflow processes being affected are limited, then the Mobile user can navigate to the Bus Process Admin > Workflow Deployment view > delete the existing active workflow process. Then, re-activate the workflow process, which will create the row S_WFA_DEFN_LOG in the local Db. If the workflow process has runtime events, then follow up to reload runtime event.








A follow-up issue is raised for the error message:





"A Workflow Monitor Definition Level was not found.(SBL-BPR-00236)"





This error message occurred in the scenario where the record from S_WFA_DEFN_LOG was missing and the active workflow had Monitoring Level > 0.





....


Message 4

[4/4]








The error message is misleading, it should have indicated that 1) "No Monitor Instance record found for this workflow process ... ", instead of saying that the 2) "Workflow Monitor Definition Level was not found".





The former (1) made it very clear why the workflow failed. The latter (2) made it sound like the Monitoring Level value from the picklist was missing or not valid.





An enhancement request has been raised to improve the error message:





CR # 10495937 : Improve error message "A Workflow Monitor Definition Level was not found.(SBL-BPR-00236)"








Search keywords: A Workflow Monitor Definition Level was not found, SBL-BPR-00236, S_WFA_DEFN_LOG, monitoring level, Workflow Instance Monitor view, replication, all, deploy, activate, local database, mobile user





.




















Applies to:

Product Release: V7 (Enterprise)


Version: 7.7.2 [18325]


Database: Oracle 9.2.0.2


Application Server OS: Microsoft Windows 2000 Advanced Server SP 3


Database Server OS: Sun Solaris 2.7





This document was previously published as Siebel SR 38-1616222341.


Symptoms

SBL-BPR-00236

Hi,
I’m trying to simulate the customized workflow process in Siebel Tools. When I click the

"Start" button the run-time instance of my Siebel client starts up and connects to the server.

The client opens, then after some time, I get pop-up message: “Process terminated. Please check

the Watch Window”. Error message in the Watch Window is : “A Workflow Monitor Definition Level

was not found. (SBL-BPR-00236)”.

Thanks, please respond to Larisa Prohorova

(larisa.prohorova.external@fujitsu-siemens.com)

Regards,
Larisa




Solution

Message 1

For the benefit of other readers, the user encountered the following error in the Simulator Watch box, when simulating a Workflow Process imported from a 7.5 a environment into 7.7.2:





“A Workflow Monitor Definition Level was not found. (SBL-BPR-00236)”.





For this behaviour, it was determined that after the import the workflow process had ‘Auto Persist’ column set to 'Yes'.





The following actions were taken to resolve the behaviour and allow the simulation to complete successfully.





1. Revised the Workflow Process


2. Set Auto Persist to 'No'


3. Continue with the simulation








Keywords, Auto, Persist, Persistence








Siebel Technical Support






תגובות

הוסף רשומת תגובה

פוסטים פופולריים מהבלוג הזה

SBL-BPR-00191: The rowId of the active row of the primary buscomp '%1', '%2', does not match the Primary Id

Applies to: Product Release: V7 (Enterprise) Version: 7.5.3 [16157] ESN Database: Oracle 9.2.0.2 Application Server OS: Microsoft Windows 2000 Server SP 3 Database Server OS: Microsoft Windows 2000 Server SP 3 This document was previously published as Siebel SR 38-1386997031. Symptoms SBL-BPR-00191 We have a error with a workflow. This WF is excuted by policy when a particular activity is closed. The WF Business Object is 'Action'. Inside this WF, there is a subprocess that invokes a Business Service that creates a new activity. In a second subprocess, the region Id of this new activity is updated using the standar update method funcionality of Siebel workflow process. Error processing Siebel Operation for: Business Object 'Action' Business Component 'Action' Primary Id ''1-5NEI6' Operation 'Insert'(SBL-BPR-00100) -- The rowId of the active row of the primary buscomp 'Action', '1-4SNCV', does not match the Prima
המשך לקרוא

Profile Attributes and Open UI

תמונה
Yes, Profile Attributes! As the ever attentive, up-to-date Siebel CRM expert that you are when you read this, you know that in Siebel Open UI (since version 15), it is no longer allowed/supported to  set  Profile Attributes from browser-side script. But  getting  them is not a problem, since the  GetProfileAttr  function works perfectly fine. Recently I found a few vanilla Profile Attributes that came quite handy in my work in Open UI JavaScript: Navigation Type : stores the navigation type such as "NAVIGATION_TAB" ActiveViewName : does what it says on the tin IsOpenUI : returns "1" when the application runs in Open UI Is SUI Theme : when "TRUE", the application theme is Synergy (aka SUI) Position:  returns the currently active position Primary Responsibility Name : guess what this one is… Profile Image : returns the URL of the user's profile image Org.Name : returns the name of the user's organization Here's a sample line of
המשך לקרוא

FINS Data Transfer Utilities

תמונה
The best thing while working on siebel is you are never short of options. Recently we had requirement of updating a Service request from contact. Finally we did that using "EAI Siebel Adapter" business service. However during that time i came across another business service "FINS Data Transfer Utilities" popularly known as DTU business service. As i was not having prior knowledge of it going by the rule of not learning swimming lessons while drowning i decided not to go for it. Lately i have tried to explore this service and trust me it can do wonders. Here is a sample example update of Service Request from contact. We need to follow below steps in order to understand strength of this business service. 1 - Navigate to Site Map. Go to Administration - Application -> Data Map Administration tab. Create a new Record with following options: Name: Service Request Test Source Business Object: Contact Destination Business Object: Service Request Here the source business
המשך לקרוא