Symptoms

Customer has a product definition which raises an error in AttributeChanged event script:
(script skeleton"

function Cfg_AttributeChanged (ChangedAttribute)
{
   if (....) {
      TheApplication().RaiseErrorText("My error message");
  }
  ...
}
(similar scripts could be implemented on Cfg_InstInitialitize or Cfg_ChildItemChanged)

Testcase:
1) A quote line item is created with this product
2) Customers starts a configurator session via webservice BeginConfiguration
3) Product attribute is updated with call UpdateConfiguration, SetAttribute
--> this will fire upper script and should return the error "My error message" in the response of the webservice call.

Current behavior shows a different message returned. Please see response below:

What needs to be done to get the correct error message in the webservice response?

Cause

The behavior is a defect with the underlying workflow and business service error handling and is addressed with change requests:
10589842 - No error message from RaiseErrorText in webservices
This is currently fixed with V8.1.1.4 and a quickfix for V8.1.1

10586201 - RaiseErrorText() on BS does not set error code/message on the workflow
This is currently fixed with V8.1.1.3 and a quickfix for V8.1.1

Solution

The behavior will be addressed by appropriate fixes in Siebel. For details please see information behind the change request links. Please note that the underlying workflow needs to have error code and error messages defined as process properties (OOB process properties).

Using RaiseErrorText during eConfigurator session will return following WS response:
(example is shown with event Cfg_InstInitialize and message "Error was raised")

Another example for the response of the system is with 2 following events Cfg_ChildItemChanged and Cfg_ChildItemSelected. Please note that Cfg_ChildItemSelected is raised before eConfigurator engine will process the new selection while Cfg_ChildItemChanged is raised after the engine processed the selection. Therefore we have different behavior in UI for both events with RaiseErrorText() and this is mirrored in the webservice responses as well.

Siebel Technical Support
Keywords: webservice, RaiseErrorText, defect, BeginConfiguration, UpdateConfiguration

References

Applies to:

Symptoms

I set the Administrator Email Address attribute to the Response Groups and added a value to SMTP in the Comm Inbound Manager/Comm Inbound Receiver component, so that an Administrator gets a warning when a email processing fails (like you said. I am getting these eMails- Warnings, in the Siebel Administrator eMail Account :

"Erro ao executar o subprocesso 'eMail Response - Create Activity' no passo 'Create Activity Process'.(SBL-BPR-00183) N㯠頰ossl criar o registo de anexo no buscomp "Action Attachment" para o ficheiro "My Money.mny.exe" armazenado em "C:\sea752\siebsrvr\bin\incoming\ATT_D58_1_1_3F450D9F_39_0_2AB14CB2.DAT". Ocorreu um erro ao abrir o ficheiro 'C:\sea752\siebsrvr\bin\incoming\ATT_D58_1_1_3F450D9F_39_0_2AB14CB2.DAT'.(SBL-UIF-00229) The system cannot find the file specified.
Erro ao invocar o servi篠'Inbound E-mail Manager', m鴯do 'AddAttachments' no passo 'Add Attachments'.(SBL-BPR-00162)
"
* Translation : Error Executing the Subprocess 'eMail Response - Create Activity' in step 'Create Activity Process'.(SBL-BPR-00183) . Impossible to creat the Registry of the Attachment in "Action Attachment" Buscomp for file xxx in "C:\sea752\siebsrvr\bin\incoming\ATT_D58_1_1_3F450D9F_39_0_2AB14CB2.DAT". Error Opening File ..The system cannot find the file specified.Error invoking 'Inbound E-mail Manager',Mehhod AddAttachments in step 'Add Attachments'.(SBL-BPR-00162)"



Some Questions :
1 - I do believe that this is the Warning about these Failed EMails , Correct ?

2 -Isn't there any way to change these messages "Text" , to be more User Friendly and understandable ?

[continued]

Cause

This is an unsupported feature, which have been logged Enhancement Requests to address them.

Solution

Message 1

Message 2

Message 3

Applies to:

Symptoms

We are getting an error while doing upgrade promotion. For an account, we have two installed assets 'Promotion A' and 'Promotion B'.

'Promotion A' and 'Promotion B' are bundled promotions, containg some component products. For this account we raise an disconnect order for 'Promotion B' so the asset becomes Inactive. Now for the same account if we do a 'Upgrade Promotion' for 'Promotion A' we are getting the following error:

********************************************************************
Error invoking service 'SIS OM PMT Service', method 'Iterate Process For Selected Rows' at step 'Edit Related

Item'.(SBL-BPR-00162)
--
An end of file error has occurred.
********************************************************************

Solution

Message 1

Message 2

Applies to:

Symptoms

Dear Siebel support team,

The following problem could be reproduced in Vanilla 7.7.2. The status for a training course remains on confirmed even if the training course has been failed.

1. Login to Siebel ERM Administration as SADMIN and goto the Training Administration.
2. Goto Test Questions and enter a new test question.
Name: First Question, Text: First Question, Type: Multiple Choice, Points: 1. Then goto Answers and add the following:
Sequence: 1, Answer Text: Correct, Correct: TRUE, Partial Value %:50
Sequence: 2, Answer Text: Correct, Correct: TRUE, Partial Value %:50
Sequence: 3, Answer Text: Incorrect, Correct: False, Partial Value %:0
3. Set the Release flag = TRUE for the question.
4. Goto Tests and add a new record
Name: Your test, Status: Active, Scoring: Standard, Max Attempts: 2, Total Points: 1, Pass Score %: 80, Type: Certification Exam, Auto Grade: TRUE, Min Review Score: 30, Partial Grade: TRUE
5. Drill down on the test and add your previous created test question (step 2) .
6. Release the test.
7. Goto Courses and add a new record
Name: Your course, Format: Web Based, Units: 1, Hours: 1, Status: Active, Completion criteria: Test Based
8. Add the course to the test you created in step 4.
[Coninued]

Solution

Message 1

Applies to:

Symptoms

When task transaction has been disabled, setting DeferWrite=True for Siebel Operation Insert Step causes the task to give the following errors:

SBL-BPR-00187, SBL-BPR-00100, SBL-DAT-60217

The specific error message is:

Note that <step name> shown above is a placeholder for the step where the error occurs.

These errors occur in the task when the Siebel Operation step with DeferWrite=True in the task is reached.

Cause

DeferWrite =True is not supported when task transaction has been disabled.

When task transaction has been disabled, DeferWrite=True should not be used.

Note that there are two cases for this, as task transaction can be disabled in two ways:

1. Task Transaction disabled for the entire Task.
   
   When task transaction has been disabled at task level, by setting the Transactional task property to FALSE, then DeferWrite=True should NOT be used in any Siebel Operation INSERT steps in that specific task.
   
   
2. Task Transaction disabled at the Business Component Level.
   
   When task transaction has been disabled at Business Component level, by setting Immediate Commit In Task user property to TRUE for a specific Business Component, then DeferWrite=True should NOT be used in any Siebel Operation INSERT steps which are based on that specific Business Component in any Task.

A new documentation change request BUG 10587397  has been submitted to request that this information be added to bookshelf.

Disabling Task Transaction should be done only when needed and thoroughly tested, as noted in the Siebel Bookshelf, Business Process Framework: Task UI Guide.

Solution

When task transaction has been disabled, then DeferWrite=True should not be used. 

Workaround:

When Task Transaction needs to be disabled, DeferWrite can be set to False on the Siebel Operation INSERT step which is affected by this. Please reference the two cases described above in the Cause section of this document.

When DeferWrite = False, then all of the required fields for that Business Component must be provided some values inside the Siebel Operation step. These values can then be updated by the user in the subsequent Task Views. As mentioned above, this will need to be thoroughly tested.

References

Applies to:

Symptoms

Cause

Solution

References

Applies to:

Symptoms

Basically what we do is we try to pause and resume the task many times. and the error "An error has occurred while restoring task instance '1-5FLU5'.(SBL-BPR-00536)" was produced.
Step to reproduce:

1. Initiate the tas
2. Click next
3. Click pause
4. Go to Inbox view
5. Resume the task
6. Click Pause
7. Click next or previous
8. Try to repeat step 5 to 7 to produce this error:
An error has occurred while restoring task instance '1-5FLU5'.(SBL-BPR-00536)

Cause

Solution

In order to workaround the problem in your system we recommend to disable the pause button for all task views in the affected tasks except one. This will avoid the scenario that leads to the error messages. You can do this by setting the task step attribute "Disable Pause".

Created FR 12-1QYIXBD for 8.0.0.2 QF ENU under the CR#10551424.

FR has been fixed, 8.0.0.2 [20412] QF0283 BugID: SBA: 7611911

References

Symptoms

Cause

Solution

References

Symptoms

Cause

Solution

References

Applies to:

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-BPR-00530: An internal error has occured while handling the following exception. The current task has been canceled as a result.

Scope

This document is informational and intended for any user.

SBL-BPR-00530: An internal error has occured while handling the following exception. The current task has been canceled as a result.

Explanation

Corrective Action

Applies to:

Goal

In TBUI when the task flow reaches an error step the following error is displayed:

[1] An internal error has occured while handling the following exception. The current task has been canceled as a result.(SBL-BPR-00530)
[2] <custom error message>(SBL-BPR-00131)

Can the first error be translated or changed?

Solution

The first error message (SBL-BPR-00530) displayed in a error step is hard coded and can not be changed. The error message passed to the custom error appears in the second error displayed (SBL-BPR-00131).

CR#10560755 has been opened to enhance the product so that the first error message displayed can be changed.