Closing Service Request – Scriptless Siebel

(11 votes, average: 4.64 out of 5)

Loading ...

Viewed : 15,779 times

Written on April 8, 2009 by neel in Scriptless Siebel

<< Previous in series Next in series >>

I am back again with scriptless Siebel series, few days ago I came across a requirement which was as following:

Requirement:

We have Service Request (Parent BC) and Activities (Child BC) when all the activities are ‘Closed’ (status set as closed) Status of SR should automatically change to ‘Closed’.

Scriptless Solution:

I thought about the solution on the same lines as described in the previous post of Scriptless Siebel series. Here are steps to achieve that:

Workflow Steps:

Query for Activities using PRM ANI Utility Service (QueryBusComp method)
Use following Search Spec [Status] <> ‘Closed’ AND [Activity SR Id] = GetProfileAttr(‘SRId’)
Decision Step will have following condition
If Number of Records greater than 0 then go to End else use Siebel Operation Step to Update SR status as Closed

Download Actual Workflow.

Runtime Event Details: Runtime events details are also very similar to last post, so you can refer to last post for screenshots.

Event Detail:
Sequence: -1
Object Type: BusComp
Object Name: Action
Event: WriteRecord
Conditional Expression: GetProfileAttr(’Me.ActiveViewName’) = ‘Service Request Detail View’
[To limit the execution to just that particular view]
Action Set Name: UpdateServiceRequest

Action Set Details:

You need to create two action records for this action set. One will set a profile attribute and other will call the workflow process

Action Details:

Name: SRId
Action Type: Attribute Set
Sequence: 1
Profile Attribute: SRId
Set Operator: Set
Value: [Activity SR Id]
Name: CallWF
Action Type: BusService
Sequence: 2
Business Service Name: Workflow Process Manager
Business Service Method: RunProcess
Business Service Context: “ProcessName”, “NewServiceRequestUpdateWF”

<< Previous in series Next in series >>

18 Comments - Leave a comment!

Visitors to this post, also read:

Deepak

Hi just sharing another thought on the same…
Neel , can you please validate if this method correct for the requirement.

1) Create link between SRequest and Activities.
In Link search spec : giv condition to check status != ‘Closed’

2) Use Count(MVL) , IF Count(MVL)=0 , then update SR as ‘Closed’
Deepak

Hi just sharing another thought on the same…
Neel , can you please validate if this method correct for the requirement.

1) Create link between SRequest and Activities.
In Link search spec : giv condition to check status != ‘Closed’

2) Use Count(MVL) , IF Count(MVL)=0 , then update SR as ‘Closed’
http://siebelunleashed.com/ neel

There are quite a few things that I would like to say about this approach.

There is already a link that exsists between SR and Activity that is why they are parent and child. You cannot give search spec in that link coz it not display all the activities which is not correct.

You need to create an MVL based on alerady existing link and try to use Type Field and Type value in MVL to restrict record.

then you can use Count(MVL) to get count but then again how will you update SR status… On Field Update user property will not work here as it works only when you manually update a field .. calculated field doesn’t work.

I hope now you understand the glitches in approach that you saying… Workflow approach is lot cleaner and also flexible.

For example in future if they say that SR should only be closed if it has solution record associated to it and also child SR if any should be closed then only you can close SR.

We can extend workflow to include all these things but MVL will not work here
http://siebelunleashed.com neel

There are quite a few things that I would like to say about this approach.

There is already a link that exsists between SR and Activity that is why they are parent and child. You cannot give search spec in that link coz it not display all the activities which is not correct.

You need to create an MVL based on alerady existing link and try to use Type Field and Type value in MVL to restrict record.

then you can use Count(MVL) to get count but then again how will you update SR status… On Field Update user property will not work here as it works only when you manually update a field .. calculated field doesn’t work.

I hope now you understand the glitches in approach that you saying… Workflow approach is lot cleaner and also flexible.

For example in future if they say that SR should only be closed if it has solution record associated to it and also child SR if any should be closed then only you can close SR.

We can extend workflow to include all these things but MVL will not work here
VerteX

What would I do in that case:

1. Create 2 user properties in Activity:
Name: On Field Update Invoke 1
Value: “Status”, “Activity”, “WriteRecord”

Name: On Field Update Invoke 2
Value: “Status”, “Service Request”, “UpdateStatus”, “[Status] = ‘Closed’”

2. Create an user property in Service Request
Name: Named Method 1
Value: “UpdateStatus”, “SET”, “Status”, “IIF (NOT BCHasRows (‘Action’, ‘Action’, ‘[Activity SR Id] = ” + [Id] + ” AND [Status] ‘Closed’, ‘All’), ‘Closed’, [Status])”

I assume you would you have to put quotes around Id value in “…[Activity SR Id] = ” + [Id] + ” AND…” but I don’t remember the syntax here, double quotes or smthng
VerteX

What would I do in that case:

1. Create 2 user properties in Activity:
Name: On Field Update Invoke 1
Value: “Status”, “Activity”, “WriteRecord”

Name: On Field Update Invoke 2
Value: “Status”, “Service Request”, “UpdateStatus”, “[Status] = ‘Closed’”

2. Create an user property in Service Request
Name: Named Method 1
Value: “UpdateStatus”, “SET”, “Status”, “IIF (NOT BCHasRows (‘Action’, ‘Action’, ‘[Activity SR Id] = ” + [Id] + ” AND [Status] ‘Closed’, ‘All’), ‘Closed’, [Status])”

I assume you would you have to put quotes around Id value in “…[Activity SR Id] = ” + [Id] + ” AND…” but I don’t remember the syntax here, double quotes or smthng
Deepak

Yeah i realize the practical infeasibilty..
Thanks for your detail insights on that.

just one more question athough related to post on scriptless part 2

i just read on comments we can call DVM through WF using
BS : Data Validation Manager and method : validate.

But where do we mention the particular Rule set Name and how do
we capture back the error message to WF

-deepak
Deepak

Yeah i realize the practical infeasibilty..
Thanks for your detail insights on that.

just one more question athough related to post on scriptless part 2

i just read on comments we can call DVM through WF using
BS : Data Validation Manager and method : validate.

But where do we mention the particular Rule set Name and how do
we capture back the error message to WF

-deepak
Reshmi

Hi All,

Pls try this option.

1. Create a MVL between SR & Activity
2. Create a MVF based on above MVL on Status field
3. Create a calculated field in SR BC as IIf(Exists([Action Status]) “Closed”, “Open”, Closed”)
5. Create a user property as On Field Update in SR BC with Status field based on above calculated field
Reshmi

Hi All,

Pls try this option.

1. Create a MVL between SR & Activity
2. Create a MVF based on above MVL on Status field
3. Create a calculated field in SR BC as IIf(Exists([Action Status]) “Closed”, “Open”, Closed”)
5. Create a user property as On Field Update in SR BC with Status field based on above calculated field
Ersin ERSOY

Hi,

Thanks for this post.

I want to ask you that why you did not used Siebel Operation to query BC instead of PRM ANI Utility Service’s QueryBusComp method ?

Regards.
Ersin ERSOY

Hi,

Thanks for this post.

I want to ask you that why you did not used Siebel Operation to query BC instead of PRM ANI Utility Service’s QueryBusComp method ?

Regards.
http://siebelunleashed.com/ neel

I guess you didn’t read the previous post in series.

I implemented this in Siebel 7.8 and in this version Siebel Query operation doesn’t return count of records. I needed count to achieve this that is PRM ANI Utility Service
http://siebelunleashed.com neel

I guess you didn’t read the previous post in series.

I implemented this in Siebel 7.8 and in this version Siebel Query operation doesn’t return count of records. I needed count to achieve this that is PRM ANI Utility Service
Bhagya

Can you please explain the detailed difference between ContinueOperation and ContinueOperation in Scrpting.
Bhagya

Can you please explain the detailed difference between ContinueOperation and ContinueOperation in Scrpting.
Rakesh

In 7.7 and above for counting records one can use the following code:
with (bc)
{
ClearToQuery();
ActivateField(“Name”);
SetSearchSpec (“Name”, “A*”);
ExecuteQuery ();
var count = CountRecords();
}
Gurdeep Singh

Hi
This post might be late but i have implemented this requirement using DVM which does not require any SRF changes.
Below are the steps:
In Adminstration – Data Validation:
Create a new Rule set as:
Name: VF Activity SR Update
BC: Service Request
BO: Service Request
Status: Active
Step off the record and drilldown on the hyperlink field Name.

It takes you to FINS Validation Rules View:
Go to Rules Tab:
Click New Record:
Name: VF Service Request
Expression: [Status] ‘Closed’
BC: Service Request
Apply To : Current Record
Return Code: Ok (Create this code in Validation messages of this Admin – data validation)
Immediate Display: FALSE

Create another New record in same instance:
Name: VF Service Request Activity

Expression: [Status] = ‘Closed’

BC: Action

Apply To : All Records

Return Code: Ok (Create this code in Validation messages of this Admin – data validation)

Immediate Display: FALSE

Create another New record:
Name: VF Service Request update

Expression: Set to nothing

BC: Service Request

Apply To : Current Record

Return Code: Ok (Create this code in Validation messages of this Admin – data validation)

Immediate Display: FALSE

Highlight the “VF Service Request update” record and click on “Actions” tab below:
Create a new Record:
Type: BC
BC : Service Request
Go to Field Values applet title below and add a new record:
Field: Status
Value: Closed

Now go to Administration-Run time Events:
Create a new Action set:
Object type: BusComp
Object name: Action
Event: WriteRecord
Action set name: VF Act Update

Action sets:
Name: VF Act Update
Action type: Business service
Business service Name: Data Validation Manager
Business service Method: Validate
Business service Context: “Rule Set Name”, “VF Activity SR Update”

Reload Rum time Events and we are done.

Closing Service Request – Scriptless Siebel

Related Posts

Visitors to this post, also read: