Workflow Rule Condition : impact of the "LookupValue"

Hello,
I would like to know something about he "LookupValue" (eg.1) impact in the "workflow rule condition". What is exactly the role of the "LookupValue"? Does it have an impact if I decide to delete it and just write the value needed (eg. 2) ?
eg.1 : ... =LookupValue("OCC_CUST_LOV_OPTY_4", "Value Needed")
eg.2 : ... =("Value Needed")
Could someone help me?
Thanks and regards.
Edited by: user5840933 on 5 mars 2009 03:44

Hi !
The lookupValue function is very useful. Imagine you created 10 workflows with a condition such as : PICKLIST="Value".
Then imagine you have to modify the "Value" of this picklist in "Value2" for example. This means you will have to update your 10 workflows to put "Value2" instead of "Value".
Using the LookupValue function, it will automatically get the picklist value based on the code corresponding to the value.
LookupValue(PICKLIST, "A") will return the value corresponding to the code "A", no matter what the value is.
In the expression builder, after chosing the field in the picklist, click on the link "Get acceptable values". Then click on a value and the LookupValue function will appear in your expression.
Hope this will help, feel free to ask more !
Max
[See Mike L announcement|http://forums.oracle.com/forums/ann.jspa?annID=883]

Similar Messages

Help writing a workflow rule

Hello Experts!!!
I need help writing a workflow rule condition to trigger the workflow. What I am aiming for is an email to be sent out when an opportunity is marked Closed/Won. But it can only be of a certain opportunity type (we use three options) and opportunity sub-type (we use two options) (these are custom fields we use)
Below are the fields that need to be used:
[<SalesStage>] = Closed/Won
[<OpportunityType>] = Acute
[<plOpportunity_SubType_ITAG>] = Tech
Thanks Again!!

Hi
Try:
[<SalesStage>] = Closed/Won AND [<OpportunityType>] = Acute AND [<plOpportunity_SubType_ITAG>] ='Tech'
Note that in case of picklists it is recomended to use the lookup value and not static text like 'Tech', but both will work.
Good luck
Guy

Dbms_rule_adm does not allow creation of rule condition 4000 characters

The underlying sotrage table for streams rules has a CLOB assigned as a datatype for storing rule condition. Unfortunately, the dbms_rule_adm package has procedures that take in varchar2 which implies that the rule condition cannot be more than 4000 characters.
Also, is it possible to create a capture process specifing a rule condition that the event be captured only when certain columns of the table are modified. I've successfully done this by associating a rule set with a capture process and the rule set will contain :dml based WHERE clause. The only issue here is that if I have a table with many columns the rule condition will be more than 4000 characters. I've also tried to call a pl/sql function in the rule condition to perform the where clause operation, but the capture process stops evaluating the rule condition.
Any help is appreciated.

Sounds like a bug to me (or limitation, may be ;).
The rule 'condition' column should have been a CLOB in those procedures rather than VARCHAR2.
Have you contacted Oracle Support?
I would love to know how you resolve this issues.
Thanks.
- Kirti

Decode the Workflow Rule

Hi,
I am working on AIA, to integrate the Siebel On Demand with On Premise ... I have come across a PDF which mentions this Wokrflow Rule Condition, However I am not really sure what this condition is ...
([<plSync_Status_ITAG>] = LookupValue
("OCC_CUST_LOV_ACCOUNT_1", "Sync⇒
ON"))
OR ([<plSync_Status_ITAG>] = Lookup⇒
Value
("OCC_CUST_LOV_ACCOUNT_1", "Sync⇒
FAILED"
Could anybody please atleast guide as to what this condition checks ?

<plSync_Status_ITAG> = the field name, I would guess Sync Status. If you aren't sure and it's a custom field you can find this value by going into Field Setup - rename Fields - Advanced. pl means picklist so it's going to be a picklist field.
LookupValue("OCC_CUST_LOV_ACCOUNT_1", "Sync⇒ON") when you add a value from a picklist to a workflow it is best to add the field then the = the click Show values, when you select the value SYNC ON this is what it will add into the formula.
So your formula says Sync Status equal to Sync on OR Sync Status equal to Sync Failed.
cheers
Alex

We have three discussions forums with same subject. whenever a post gets new reply in one forum, it should automatically trigger workflow functionality to check conditions and send the same reply to other synchronized forums.

we have three discussions forums with same subject. whenever a post gets new reply in one forum, it should automatically trigger workflow functionality to check conditions and send the same reply to other synchronized forums.
Rajiv Kumar

Hi,
More details about your discussions forum will make others easier to find a corresponding solution on your requirement.
If you mean there are three Discussion Board list waiting for synchronizing, I would suggest you create an Event Receiver for the three Discussion Board list.
Here is a link with code demo about how to copy items from one Discussion Board to another including Replies:
http://spcodes.blogspot.com/2013/03/programmatically-copy-items-from-one.html
Here is a step by step sample on creating a simple Item added event receiver for Custom List in SharePoint 2010:
http://msdn.microsoft.com/en-us/library/ff398052.aspx
More information on Event Receiver for your reference:
http://msdn.microsoft.com/en-us/library/gg749858(v=office.14).aspx
http://msdn.microsoft.com/en-us/library/ff408183(v=office.14).aspx
Feel free to reply if there are still any questions.
Best regards
Patrick Liang
TechNet Community Support

Error handling in Workflow rules to determine agents.

Hi there,
I have a rule, if it fails. I need to send a SAP mail. Or skip that particular user decision step... Please.let me know what ahould be done for this.
Thanks,
Sukumar.

Basically you need to execute the rule already before the actual decision step. What kind of rule do you have? If it is based on a function module, you can copy the code from the function inside your own method, and then use this method in a separate background step before your decision step. And if the agent cannot be determined you can skip the step, or whatever you want. And if you are familiar with ABAP OO and how to use it in workflow, you can include the above-mentioned logic inside a functional method of a class, and then use a condition step (with the functional method) instead of the separate background step.
Also, if you are not using a rule that is based on a function module, you can always find a way how to programatically call the rule in your code. There are lots of examples in SDN (or WUG).
Regards,
Karri

Workflow rules doesn't work for existing record!!?!?!?

Hi all,
I've created one workflow rule to update value from one filed to another. Here is my expression:
[<QuickSearch1>] <> [<plStatus_ITAG>]
and my action is
field name = "*Status" (QuickSearch1)
Value = <plStatus_ITAG>
and I tick on the Overwrite the existing value
This is work for new record, but for the existing one the field value doesn't chnage. Any suggestion??
Thanks
Note

The syntax should be: PRE('< QuickSearch1>') <> [<QuickSearch1>] for the condition.

Creating workflow rule that can calculate open days

Hi,
Can someone help me confirm if what I'm doing is possible and if so if my syntax is correct.
I have created a field on the Service Request that calculates Service Level Agreement days.
I wish to create a new field that on close of the SR the system will calculate if Open days is greater than Service level agreement days - If it is greater them insert value "Not Met' and if less than insert value "Met".
IIf(TIMESTAMPDIFF(SQL_TSI_DAY,"Service Request"."Create Date",CURRENT_DATE) > [<nService_Level_Agreement_ITAG>],"Not Met","Met"))
However this doesn't work? Can someone help me??
thanks,

Hi,
These are functions supported in reports and not in advanced field management or workflows
You may have to write a simple workflow condition like below
[<Status>] = LookupValue("SR_STATUS", "Closed") AND ([<CreatedDate>] + [<nSLA_Days_ITAG>]) less than or equal to [<ClosedDate>]
then set the field as "Y"
Ensure the field ClosedDate is set properly on change of the status and place that as first workflow before the above
Hope it helps
-- Venky CRMIT

Unable to evaluate workflow rule - Value too long for field

Need help with a workflow error for a record update before the record is saved. There are 3 calculations that would be done in a particular order - all on number fields. Each time, I am overwriting existing values. The individual numbers could have up to 6 decimal spaces. When I try to update one or more fields that contain the calculation, I get an error message saying that the system is unable to evaluate the workflow rule - value too long for field (zNum6).
This same calculation is fine when a new record is entered and the calculation is done as a default field value.
Any ideas?

I actually had to use a ToChar function at the beginning of the calculation and #### to indicate the number of digits to make this work. Oracle Help Desk provided the answer - quickly.

How to set up rules/conditions on a drop down box to ensure its been filled if a value in a text box is selected.

Hi, I am in midst of creating a form in infopath. I have a text box field in which the user will enter the number of issues he has. if the user has entered the number of issues he has, then he will need to select the type of issues from a multi selection
box. Thus i need to know how to set up rules/conditions to ensure that the user has to complete the multi selection box if he enters a value in text box for the number of issues.

I assume what you are asking is to make multi selection box as mandatory. If not please explain with a example
Try below:
http://webcache.googleusercontent.com/search?q=cache:ItIYeZ8K2gEJ:sharepointkings.blogspot.com/2013/06/make-multi-select-list-box-required-in.html+&cd=4&hl=en&ct=clnk&gl=in&client=firefox-beta
If this helped you resolve your issue, please mark it Answered

How to delete the orphaned Expected Rule Entries exist in the FIM portal

Hi,
How to delete the orphaned Expected Rule Entries exist in the FIM portal.
A large number of orphaned Expected Rule Entries exist in the FIM portal (originally 140000k+ objects, currently 75000+ objects). They consume the a lot of FIM database space and slows down the identity lifecycle management synchronization processes.
Regards
Anil Kumar

Hello,
in my environments i use this approach:
https://social.technet.microsoft.com/Forums/en-US/1af6cf77-4c55-4a3e-93cc-0baae80bc88f/expiration-workflow-cannot-delete-ere?forum=ilm2
This sets up a compination of Sets, Workflow and MPR to let the "Expiration Workflow" delete EREs as soon as they get orphaned.
This works fine since 3 years now, even if there are comming SQL-Jobs within a FIM update, but I implemented this before this was done.
I would suggest to clear the current orphaned EREs with PowerShell to avoid request flooding when implementing the above solution. Then implement that housecleening above.
Regards
Peter
Peter Stapf - ExpertCircle GmbH - My blog:
JustIDM.wordpress.com

Workflow mails going to all the Users Maintained in the System

Hi Everyone,
I have a Purchase order workflow which gets triggered through ME21, when the PO need to be approved at every level based on the amount of PO , mail need to be sent to set of users.
We have a step in workflow , where we have created a rule and we pass the current level( eg, L1, L2,L3,L4) to the FM and this FM provides the List of Users for that level and the mail need to be sent to them.
I checked the FM that is working fine but when the workflow gets triggered it sends to every user .
Please let me know what possibly has gone wrong.
Regards,
Raj

hi,
As suggested, did you check in the rule definition, there is an option called "Terminate if Rule resolution without result" , enable and this should resolve the issue.
Since the task is defined as general task, the work item can be executed by all users. And if the rule fails, the above option is not enabled, hence it sends it to all valid users in the system.
Please try this out.
Best Regards,
Saujanya

Update Rule error while loading the data

Hello All,
I tried to do the init load for the datasource 2LIS_02_VAKON (Sales Document Condition), But it error's out in the Update rule saying:
Short text: Error when generating the update program
Long Text: Diagnosis
     An error occurred during program generation for InfoSource 2LIS_11_VAKON
     and InfoProvider 0SD_C15 . This may be extrapolated to incorrect update
     rules.
Procedure
     Check and correct your update rules and then generate the update program
     again. You can find help on the error in the error log.
The update rule looks very fine. I even deleted it and re created, but no success..... Please give me your thoughts abt it..... Any suggestions will be great for me.....

Hello Gokul,
I could'nt see any analyse button in RSMON. This is the only error message I could get from the Process monitor:
Short text: Error when generating the update program
Long Text: Diagnosis
An error occurred during program generation for InfoSource 2LIS_11_VAKON
and InfoProvider 0SD_C15 . This may be extrapolated to incorrect update
rules.
Procedure
Check and correct your update rules and then generate the update program
again. You can find help on the error in the error log.
Do you expect something else ? Also I went through your OSS note, they are asking to apply support pack 18. Is this a serious issue to apply SP? Because in Quality and Prod it loads fine......
Please let me know your idea

Workflow is not trigerred from the portal

Hi all,
I have a scenario in which the workflow requires to be trigerred through the portal and direct the task to the approver's inbox in extent to sending email notification to the approver, I have developed the custom workflow and i am using the standard rule for getting the approver. all of this is working fine when i test them on R/3 but wheni am integrating the workflow to the portal using a BAPI it is not trigerring the workflow. The first step in my worklflow is to send the email notification to the approver, if i remove this step then it directs the task to the approver's inbox which is the second step in my workflow.
Can anyomne please guide me why it is happening.
Thanks.
Saurbah Anand.

Hi,
You said
<i>"wheni am integrating the workflow to the portal using a BAPI it is not trigerring the workflow. The first step in my worklflow is to send the email notification to the approver, <b>if i remove this step then it directs the task to the approver's inbox</b> which is the second step in my workflow."</i>
Do you mean say that it is not working when you put the sendmail step alone? Or is it that the workflow is not triggering at all.
I assume that you are using a BAPI to create an event which will start this workflow. Now if your workflow is not starting at all then you need to activate the event trace (SWELS) and check whether the event was triggered first (in SWEL). If yes then check for any errors in the receiver connection.
If your workflow does start and fails at sending mail step then you may need to give some more info. Are you using the standard sendmail step or Are u using a background task. In case if u r using a BG task then it might be creating a dump while triggering from portal (Ex. it might need the Evt_creator user id to determine the approver which is not binded properly from Event<->Workflow<->Task<->Method).
Also have a look at ST22 for any dumps.
Thanks,
Prasath N

Create opportunity using workflow rule

Hi,
Is there a way to create an opportunity record using a workflow rule.
We want to be able to create a service opportunity to be triggered automatically by the sales person by either updating a flag or check box which inturn triggers
a workflow rule that can create an opportunity.
I am aware of using a web link to copy an existing opportunity.
Any ideas ?
Thanks
Swami

At this time this is possible by using Integration Events and using web services. CRMOD does not support Workflows that will automatically create an opportunity using a workflow

Workflow Rule Condition : impact of the "LookupValue"

Similar Messages

Maybe you are looking for