Scriptless Siebel – Create Activity on SetFieldValue
(9 votes, average: 4.56 out of 5)
Loading ...Requirement:
Whenever we change Account Type. We would like to create an Activity of type “Lab Test” with description as “Auto Generated Activity”
Solution:
We need to create a Workflow and a Runtime Event to complete this requirement without using eScript.
Workflow details:
Our workflow will consist of 3 steps and will be based on Account BO
- Start Step
- Siebel Operation Step (Insert)
- End Step
I am attaching the Workflow XML that you can download and see the workflow for your self
Runtime Event Details:
We need to setup a Runtime Event on SetFieldValue of Account BC.
Event Detail:
- Sequence: 1
- Object Type: BusComp
- Object Name: Account
- Event: SetFieldValue
- Subevent: Type
- Action Set Name: CreateAccountActivity
Action Sets:
- Name: CreateAccountActivity
- Action Type: BusService
- Business Service Name: Workflow Process Manager
- Business Service Method: RunProcess
- Business Service Context: “ProcessName”, “CreateAccountActivity”
Just deploy the workflow and you are done. You can add more fields if you want to and more conditions to restrict creation of activity because with this setup an Activity will be created every time you change the value of field “Type” on Account.
<< Previous in series
what is the use of such an empty news …
next time we will see how to add a field on a applet …
2 bob: It can be useful for someone, who want to understand how to configure Scriptless Siebel and didn’t understand where to start from.
Normally this sort of requirement should have been refined before commiting to the business. Changing the field would do something in other bc is detrimental as what would happen if I would press Esc or undo the record after I change the Account Type.
Thx
Dos
Part 1
Regarding Dos's comment, what if the user accidently changes the Account Type, and then after editing other fields, prior to the save of the record changes the account type back to the original value, the workflow will still have fired and an invalid activity was created.
I believe it is better design to only execute automation such as this after the record has been committed. Therefore can you please provide the way to develop this with a scriptless solution that will execute the workflow after the commit if the Account Type has been as per requirement. My suggestion would be to have a runtime event on SetFieldValue which would set a profile attribute to flag that the Account Type has been updated. If the user then updates the account type to be back to the previous value prior to commit however then the profile attribute would have to be reset. Therefore there must be some logic in this process to know what the value of Account Type is prior to the record being edited.
Part 2
Also in the theme of scriptless siebel, I would like to know how you would go about an additional requirement. Let's say that the client wants this automation to happen in real time and the client would like to see the updated data immediately after the activity is created. Ie. If the user is in an Oppurtunity > Activities detail view or if there exists an activities MVG on the current oppurtunity view then the client would like to see this data immediatly. How could this be implemented through the scriptless siebel solution? ……Quite often I receive this sort of requirement from the client.
Also to throw it out there, I would like to know if it is po
Josh,
I have been thinking about it.. but haven’t had a chance to actually try something.
Solution suggested by you also came in my mind but it doesn’t feel right.. too many profile attributes and too many events will need to be taken care.
I am sure there is a better solution for this and is definitely worth finding.
I am not sure what you mean by
It does happen in real time and you immideatly start seeing the created activity.
I think I am missing something here
Hi Neel
“client would like to see the updated data immediately after the activity is created”
I just wanted to iterate that if the automation was to occur in the background (such as a workflow invoked which would create the record out of context) that the current view would need to be refreshed after this automation to show the updated data.
In my updated requirement where the client want the activity to be created after the writerecord, at current the only way i know to do this is using script on the WriteRecord method. The way to create the new activity would be to instantiate the activity BC out of context and create the activity. However then the activity would not show up in the current context. So after that there would be script to refresh the current applet using FINS Teller UI Navigation business service RefreshCurrentApplet method.
In your scriptless solution, does this create the activity in the current context so that if you were in an Oppurtunity > Activities detail view and you updated the Account Type field it would show the new activity in the detail view list immediately? (im not sure i havent tried the solution).
Yes, it shows the activity immediately…I have tested it
The reason is, if a workflow is executed through runtime event or user property then the current business context is passed to the workflow due to BO given while creating the workflow record.
And my workflow uses Siebel Operation – Insert method which means it is creating the record in context of Active BO so it reflects immediately.
Leave your response!
Polls
Recent Posts
Get updates by Email
Friends
History
Categories
Siebel Unleashed on Twitter
Posting tweet...
Powered by Twitter Tools
Most Voted
Most Commented
Most Viewed
Canonical URL by SEO No Duplicate WordPress Plugin
Powered by WordPress | Log in | Entries (RSS) | Comments (RSS) | Arthemia theme by Michael Hutagalung 66 queries. 0.914 seconds.