Configuring Workflows for the Producer Success Model

This chapter describes how to configure workflow rules to support the Producer Success Model in Oracle CRM On Demand Financial Services Edition. It includes the following topics.

About Configuring Workflows for the Producer Success Model

In Oracle CRM On Demand, you can use workflow rules to specify that one or more actions must be performed automatically each time a specified event occurs. You can configure as many workflow rules as you want to implement your business processes.

The Producer Success Model in Oracle CRM On Demand is a framework that uses workflow rules to automate the creation of activities, allowing insurance agents or financial advisors to follow up their leads and stay in touch with their clients on a regular basis.

In the Producer Success Model, the following terms are used:

Producer. A producer is an insurance agent or financial advisor.
Client. A client is a contact with whom your company maintains a relationship on a long-term basis so that you can monitor changes in the client's situation and identify opportunities to cross-sell additional products to the client. Clients usually also seek advice on which products fit their needs.

To support the Producer Success Model, you configure a set of workflow rules and actions. The workflow rules that are specific to the Producer Success Model include:

A workflow rule that creates a task to call the lead on the next working day every time a new Lead record is created. For more information about this workflow rule, see Workflow Rule for Creating a Referral Call When a New Lead is Created.
Workflow rules that create a followup task to call a lead, based on the value in the Call Result field in the Task Detail page. For more information about these workflow rules, see Workflow Rules for Creating Followup Calls Based on Call Results.
Workflow rules that create tasks to help producers to keep in regular contact with clients. For more information about these workflow rules, see Workflow Rules for Scheduling Calls with Clients.

For more information about Producer Success Model workflows, see 1801375.1 (Article ID) on My Oracle Support or from Oracle CRM On Demand — Training and Support Center.

Configuring Workflow Rules and Actions for the Producer Success Model

The following procedures describe the workflow rules and actions that you must create to support the Producer Success Model:

To create a workflow rule, complete the following procedure.

To create a workflow rule

In Oracle CRM On Demand, click Admin.
In the Business Process Management section, click Workflow Configuration.
In the Workflow Rules List page, click New on the title bar.
In the Workflow Rule Name field, enter a unique name.
To make the workflow rule active, select the Active option.
In the Record Type menu, select the appropriate record type.
In the Trigger Event menu, select the appropriate trigger event.
(Optional) In the Workflow Rule Condition section of the Workflow Rule Detail page, click the fx icon and add an expression.
Save the rule.

Creating a Workflow Action

To create a workflow action, complete the following procedure.

To create a workflow action

In the Workflow Rule Detail page, in the Actions title bar, click Menu and select Create Task.
In the Workflow Action Edit page, enter a name for the action.
If you want to enable the action, select the Active check box.
In the Owner menu, select Relative User on Record, and then select the appropriate task owner.
In the Type menu, select the appropriate task type.
In the Due Date menu, enter the expression that evaluates to the appropriate due date for the task.
You can use Expression Builder to create the expression. Click the fx icon beside the field to open the Expression Builder window.
In the Subject field, enter the subject.
Save the action.

Repeat these procedures until you have configured all of the necessary workflow rules and actions.

For more information about configuring workflow rules and actions, see Oracle CRM On Demand Online Help.

Workflow Rule for Creating a Referral Call When a New Lead is Created

This topic provides details of the workflow rule and action that you must configure so that a task is automatically created when a lead record a saved for the first time. A referral call is created. It is scheduled on the next working day after the lead is created. For example, if the lead is created on a Friday or Saturday, the call is scheduled for the following Monday. The owner of the task is the owner of the lead record.

Note: The expressions in this topic might appear across several lines due to length. All expressions in this topic must be entered in Expression Builder as one line and cannot contain any spaces. Also, the language-independent field names and the field-name syntax used in the expressions in this topic are the field names and syntax that were used in Expression Builder in releases earlier than Release 29 Service Pack 1. These expressions are still valid in Release 29 Service Pack 1 and later releases. However, starting with Release 29 Service Pack 1, Expression Builder uses language-independent field names and a field-name syntax that are different from the field names and the field-name syntax used in earlier releases. So, if you select the corresponding fields from the field list in Expression Builder when you create or update an expression in Release 29 Service Pack 1 or a later release, then the field names in the expression will be different from the field names shown in this topic, and the fields will appear in the expression editor with the following syntax: [{FieldName}]. It is recommended that you always select the fields for your expressions from the list of fields in Expression Builder, so that the field names and the field syntax are always correct. For more information about Expression Builder, see Oracle CRM On Demand Online Help.

Workflow Rule Details

This topic describes the details of the workflow rule.

Record Type

The record type is a Lead record.

Trigger Event

The trigger event is When New Record Saved.

Rule Condition

Not applicable. Leave this section blank.

Workflow Action Details

This topic describes the details of the workflow action.

Action Type

The action type is Create Task.

Task Type

The task type is a Referral Call.

Due Date

The Due Date field contains a numeric value that is calculated by adding the value in this field to the date on which the task is created.

Enter the following expression in the Due Date field:

IIf((IfNull(Mid(1.0 * JulianDay(Today()+1)/7, 8, 1), "0")>="7"),IIf((IfNull(Mid(1.0 * JulianDay
(Today()+1)/7, 8, 1), "0")="7"),Today()+3,Today()+2),Today()+1)

Subject

The subject field contains the subject line for the task. You can embed functions and field names in the text. Three percent signs (%%%) before and after an embedded function or field name indicate that it is to be converted to a string.

Caution: In the Subject field, three percent signs (%%%) are placed before and after the functions and field names. If you type a function or field name directly in the Subject field, you must type three percent signs before and after it. If you use Expression Builder to embed a function or field name, the percent signs are automatically added and must not be pasted into Expression Builder. When percent signs are pasted into Expression Builder, Expression Builder displays an internal error.

For more information about expressions, see Oracle CRM On Demand Online Help.

Enter the following expression in the Subject field:

%%%LookupValue("TODO_TYPE", "Referral Call")%%%-%%%JoinFieldValue('<Lead>',[<LeadId>],
'<LeadFullName>')%%%

Workflow Rules for Creating Followup Calls Based on Call Results

This topic provides details of the workflow rules and actions that you must configure so that a followup task is created when a producer updates the value in the Call Result field in the Task Detail page after making a call to a lead or a client.

The types of calls that producers make to leads or clients include the following:

Referral calls. Referral calls are calls that producers must make to follow up on leads.
Birthday calls. Birthday calls are calls that producers make to existing leads or clients on their birthday.
Review calls. Review calls are calls that producers make to leads or clients when it has been six months since the last call with the lead.

The producer can capture the result of these calls in the Call Result field on the Task Detail page. The values for the Call Result field include the following:

No Reach. The producer selects this value if the lead is unreachable.
Stay In Touch. The producer selects this value if the lead or contact does not want to talk today but the lead wants the producer to stay in touch.
Dead File. The producer selects this value if the lead does not want to talk today and does not want to be contacted again
Appointment. The producer selects this value if the lead or client is ready for an appointment.

The workflow rules in this topic create a followup task for calls that result in the No Reach value or the Stay in Touch value. The type of the followup task depends on the type of the original task.

Call result value is No Reach. If the Call Result value is No Reach, the workflow rule schedules a followup task for the next working day for the lead or client record owner.
Call result value is Stay in Touch. If the Call Result value is Stay in Touch, the workflow rule schedules a followup task to call the lead six months from now or one week prior to the lead’s or client’s birthday, whichever occurs first.

Followup Calls for Referral Calls Where the Result Is No Reach

This workflow rule is triggered when a producer calls a lead through a referral call and then updates the Call Result field in the Task edit page to No Reach. The workflow rule creates a referral call followup task for the following workday.

Note: The expressions in this topic might appear across several lines due to length. All expressions in this topic must be entered in Expression Builder as one line and cannot contain any spaces. Also, the language-independent field names and the field-name syntax used in the expressions in this topic are the field names and syntax that were used in Expression Builder in releases earlier than Release 29 Service Pack 1. These expressions are still valid in Release 29 Service Pack 1 and later releases. However, starting with Release 29 Service Pack 1, Expression Builder uses language-independent field names and a field-name syntax that are different from the field names and the field-name syntax used in earlier releases. So, if you select the corresponding fields from the field list in Expression Builder when you create or update an expression in Release 29 Service Pack 1 or a later release, then the field names in the expression will be different from the field names shown in this topic, and the fields will appear in the expression editor with the following syntax: [{FieldName}]. It is recommended that you always select the fields for your expressions from the list of fields in Expression Builder, so that the field names and the field syntax are always correct. For more information about Expression Builder, see Oracle CRM On Demand Online Help.

Workflow Rule Details

This topic describes the details of the workflow rule.

Record Type

The record type is an Activity record.

Trigger Event

The trigger event is When Modified Record Saved.

Rule Condition

The Workflow Rule Condition field contains the workflow rule condition.

Enter the following expression in the Workflow Rule Condition field:

[<Type>]=LookupValue("TODO_TYPE", "Referral Call") AND [<CallResult>]=LookupValue("OD_CALL_RESULT", 
"No Reach") AND PRE('<CallResult>') IS NULL

Workflow Action Details

This topic describes the details of the workflow action.

Action Type

The action type is Create Task.

Task Type

The task type is a Referral Call.

Due Date

The Due Date field contains a numeric value that is calculated by adding the value in this field to the date on which the task is created.

Enter the following expression in the Due Date field:

IIf((IfNull(Mid(1.0 * JulianDay(Today()+1)/7, 8, 1), "0")>="7"),IIf((IfNull(Mid(1.0 * JulianDay
(Today()+1 )/7, 8, 1), "0")="7"),Today()+3,Today()+2),Today()+1)

Subject

The Subject field contains the subject line for the task. You can embed functions and field names in the text. Three percent signs (%%%) before and after an embedded function or field name indicate that it is to be converted to a string.

Caution: In the Subject field, three percent signs (%%%) are placed before and after the functions and field names. If you type a function or field name directly in the Subject field, you must type three percent signs before and after it. If you use Expression Builder to embed a function or field name, the percent signs are automatically added and must not be pasted into Expression Builder. When percent signs are pasted into Expression Builder, Expression Builder displays an internal error.

For more information about expressions, see Oracle CRM On Demand Online Help.

Enter the following expression in the Subject field:

%%%LookupValue("TODO_TYPE", "Referral Call")%%%-%%%JoinFieldValue('<Lead>',[<LeadId>],
'<LeadFullName>')%%%

Followup Calls for Review Calls Where the Result Is No Reach

This workflow rule is triggered when a producer calls a lead or client through a review call and then updates the Call Result field in the Task edit page to No Reach. The workflow rule creates a review call followup task for the following workday.

Note: The expressions in this topic might appear across several lines due to length. All expressions in this topic must be entered in Expression Builder as one line and cannot contain any spaces. Also, the language-independent field names and the field-name syntax used in the expressions in this topic are the field names and syntax that were used in Expression Builder in releases earlier than Release 29 Service Pack 1. These expressions are still valid in Release 29 Service Pack 1 and later releases. However, starting with Release 29 Service Pack 1, Expression Builder uses language-independent field names and a field-name syntax that are different from the field names and the field-name syntax used in earlier releases. So, if you select the corresponding fields from the field list in Expression Builder when you create or update an expression in Release 29 Service Pack 1 or a later release, then the field names in the expression will be different from the field names shown in this topic, and the fields will appear in the expression editor with the following syntax: [{FieldName}]. It is recommended that you always select the fields for your expressions from the list of fields in Expression Builder, so that the field names and the field syntax are always correct. For more information about Expression Builder, see Oracle CRM On Demand Online Help.

Workflow Rule Details

This topic describes the details of the workflow rule.

Record Type

The record type is an Activity Record.

Trigger Event

The trigger event is When Modified Record Saved.

Rule Condition

The Workflow Rule Condition field contains the workflow rule condition.

Enter the following expression in the Workflow Rule Condition field:

[<Type>]=LookupValue("TODO_TYPE", "Review Call") AND [<CallResult>]=LookupValue("OD_CALL_RESULT", 
"No Reach") AND PRE('<CallResult>') IS NULL

Workflow Action Details

This topic describes the details of the workflow action.

Action Type

The action type is Create Task.

Task Type

The task type is a Review Call.

Due Date

The Due Date field contains a numeric value that is calculated by adding the value in this field to the date on which the task is created.

Enter the following expression in the Due Date field:

IIf((IfNull(Mid(1.0 * JulianDay(Today()+1)/7, 8, 1), "0")>="7"),IIf((IfNull(Mid(1.0 * JulianDay
(Today()+1 )/7, 8, 1), "0")="7"),Today()+3,Today()+2),Today()+1)

Subject

The Subject field contains the subject line for the task. You can embed functions and field names in the text. Three percent signs (%%%) before and after an embedded function or field name indicate that it is to be converted to a string.

Caution: In the Subject field, three percent signs (%%%) are placed before and after the functions and field names. If you type a function or field name directly in the Subject field, you must type three percent signs before and after it. If you use Expression Builder to embed a function or field name, the percent signs are automatically added and must not be pasted into Expression Builder. When percent signs are pasted into Expression Builder, Expression Builder displays an internal error.

For more information about expressions, see Oracle CRM On Demand Online Help.

Enter the following expression in the Subject field:

%%%LookupValue("TODO_TYPE", "Review Call")%%%-%%%IIf([<PrimaryContactId>] <> "No Match Row Id",
JoinFieldValue('<Contact>',[<PrimaryContactId>],'<ContactFullName>'),JoinField Value
('<Lead>',[<LeadId>],'<LeadFullName>'))%%%

Followup Calls for Birthday Calls Where the Result Is No Reach

This workflow rule is triggered when a producer calls a lead or client through a birthday call and then updates the Call Result field in the Task edit page to No Reach. The workflow rule creates a review call followup task for the following workday.

Note: The expressions in this topic might appear across several lines due to length. All expressions in this topic must be entered in Expression Builder as one line and cannot contain any spaces. Also, the language-independent field names and the field-name syntax used in the expressions in this topic are the field names and syntax that were used in Expression Builder in releases earlier than Release 29 Service Pack 1. These expressions are still valid in Release 29 Service Pack 1 and later releases. However, starting with Release 29 Service Pack 1, Expression Builder uses language-independent field names and a field-name syntax that are different from the field names and the field-name syntax used in earlier releases. So, if you select the corresponding fields from the field list in Expression Builder when you create or update an expression in Release 29 Service Pack 1 or a later release, then the field names in the expression will be different from the field names shown in this topic, and the fields will appear in the expression editor with the following syntax: [{FieldName}]. It is recommended that you always select the fields for your expressions from the list of fields in Expression Builder, so that the field names and the field syntax are always correct. For more information about Expression Builder, see Oracle CRM On Demand Online Help.

Workflow Rule Details

This topic describes the details of the workflow rule.

Record Type

The record type is an Activity record.

Trigger Event

The trigger event is when Modified Record Saved.

Rule Condition

The Workflow Rule Condition field contains the workflow rule condition.

Enter the following expression in the Workflow Rule Condition field:

[<Type>]=LookupValue("TODO_TYPE", "Birthday Call") AND [<CallResult>]=LookupValue("OD_CALL_RESULT", 
"No Reach") AND PRE('<CallResult>') IS NULL

Workflow Action Details

This topic describes the details of the workflow action.

Action Type

The action type is Create Task.

Task Type

The task type is a Review Call.

Due Date

The Due Date field contains a numeric value that is calculated by adding the value in this field to the date on which the task is created.

Enter the following expression in the Due Date field:

IIf((IfNull(Mid(1.0 * JulianDay(Today()+1)/7, 8, 1), "0")>="7"),IIf((IfNull(Mid(1.0 * JulianDay
(Today()+1 )/7, 8, 1), "0")="7"),Today()+3,Today()+2),Today()+1)

Subject

The Subject field contains the subject line for the task. You can embed functions and field names in the text. Three percent signs (%%%) before and after an embedded function or field name indicate that it is to be converted to a string.

Caution: In the Subject field, three percent signs (%%%) are placed before and after the functions and field names. If you type a function or field name directly in the Subject field, you must type three percent signs before and after it. If you use Expression Builder to embed a function or field name, the percent signs are automatically added and must not be pasted into Expression Builder. When percent signs are pasted into Expression Builder, Expression Builder displays an internal error.

For more information about expressions, see Oracle CRM On Demand Online Help.

Enter the following expression in the Subject field:

%%%LookupValue("TODO_TYPE", "Review Call")%%%-%%%IIf([<PrimaryContactId>] <> "No Match Row Id",
JoinFieldValue('<Contact>',[<PrimaryContactId>],'<ContactFullName>'),JoinFieldValue('<Lead>',
[<LeadId>],'<LeadFullName>'))%%%

Followup Calls for Referral or Review Calls Where the Result Is Stay in Touch and the Birthday Is Not in the Current Week and Is Within Six Months

This workflow rule is triggered when a producer calls a lead or client through a referral call or a review call and then updates the Call Result field in the Task edit page to Stay in Touch. If the birthday of the lead or client does not occur during the current week but does occur within six months, the workflow rule creates a birthday call followup task to call the lead or client a week before the birthday.

Note: The expressions in this topic might appear across several lines due to length. All expressions in this topic must be entered in Expression Builder as one line and cannot contain any spaces. Also, the language-independent field names and the field-name syntax used in the expressions in this topic are the field names and syntax that were used in Expression Builder in releases earlier than Release 29 Service Pack 1. These expressions are still valid in Release 29 Service Pack 1 and later releases. However, starting with Release 29 Service Pack 1, Expression Builder uses language-independent field names and a field-name syntax that are different from the field names and the field-name syntax used in earlier releases. So, if you select the corresponding fields from the field list in Expression Builder when you create or update an expression in Release 29 Service Pack 1 or a later release, then the field names in the expression will be different from the field names shown in this topic, and the fields will appear in the expression editor with the following syntax: [{FieldName}]. It is recommended that you always select the fields for your expressions from the list of fields in Expression Builder, so that the field names and the field syntax are always correct. For more information about Expression Builder, see Oracle CRM On Demand Online Help.

Workflow Rule Details

This topic describes the details of the workflow rule.

Record Type

The record type in an Activity record.

Trigger Event

The trigger event is When Modified Record Saved.

Rule Condition

The Workflow Rule Condition field contains the workflow rule condition.

Enter the following expression in the Workflow Rule Condition field:

([<Type>]=LookupValue("TODO_TYPE", "Referral Call") OR [<Type>]=LookupValue("TODO_TYPE", 
"Review Call")) AND [<PrimaryContactId>] = "No Match Row Id" AND [<CallResult>]=LookupValue
("OD_CALL_RESULT", "Stay In Touch") AND PRE('<CallResult>') IS NULL AND JoinFieldValue('<Lead>',
[<LeadId>],'<DateofBirth>') IS NOT NULL AND JulianDay(IIf(JulianDay(Mid(JoinFieldValue('<Lead>',
[<LeadId>],'<DateofBirth>'),1,6)+ToChar(Today(),'YYYY')) < JulianDay(Today()),Mid(JoinFieldValue
('<Lead>',[<LeadId>],'<DateofBirth>'),1,6)+ToChar(Today()+Duration("P1Y"),'YYYY'), Mid(JoinFieldValue
('<Lead>',[<LeadId>],'<DateofBirth>'),1,6)+ToChar(Today(),'YYYY')))>JulianDay(Today()+7) AND JulianDay
(IIf(JulianDay(Mid(JoinFieldValue('<Lead>',[<LeadId>],'<DateofBirth>'),1,6)+ToChar(Today(),'YYYY')) 
< JulianDay(Today()),Mid(JoinFieldValue('<Lead>',[<LeadId>],'<DateofBirth>'),1,6)+ToChar(Today()
+Duration("P1Y"),'YYYY'), Mid(JoinFieldValue('<Lead>',[<LeadId>],'<DateofBirth>'),1,6)+ToChar(Today(),
'YYYY')))<=JulianDay(Today()+Duration("P6M"))

Workflow Action Details

This topic describes the details of the workflow action.

Action Type

The action type is Create Task.

Task Type

The task type is a Birthday Call.

Due Date

The Due Date field contains a numeric value that is calculated by adding the value in this field to the date on which the task is created.

Enter the following expression in the Due Date field:

Today()+JulianDay(Mid(JoinFieldValue('<Lead>',[<LeadId>],'<DateofBirth>'),1,6)+IIf(JulianDay
(Mid(JoinFieldValue('<Lead>',[<LeadId>],'<DateofBirth>'),1,6)+ToChar(Today(),'YYYY')) < 
JulianDay(Today()),ToChar(Today()+Duration("P1Y"),'YYYY'),ToChar(Today(),'YYYY')))-JulianDay
(Today())-(IIf(IfNull(Mid(1.0*(JulianDay(Mid(JoinFieldValue('<Lead>',[<LeadId>],'<DateofBirth>')
,1,6)+IIf(JulianDay(Mid(JoinFieldValue('<Lead>',[<LeadId>],'<DateofBirth>'),1,6)+ToChar(Today(),
'YYYY')) < JulianDay(Today()),ToChar(Today()+Duration("P1Y"),'YYYY'),ToChar(Today(),'YYYY')))
-7)/7,8,1),"0")>="7",(IIf(IfNull(Mid(1.0*(JulianDay(Mid(JoinFieldValue('<Lead>',[<LeadId>],'
<DateofBirth>'),1,6)+IIf(JulianDay(Mid(JoinFieldValue('<Lead>',[<LeadId>],'<DateofBirth>'),1,6)
+ToChar(Today(),'YYYY')) < JulianDay(Today()),ToChar(Today()+Duration("P1Y"),'YYYY'),ToChar
(Today(),'YYYY')))-7)/7,8,1),"0")="7",5,6)),7))

Subject

The Subject field contains the subject line for the task. You can embed functions and field names in the text. Three percent signs (%%%) before and after an embedded function or field name indicate that it is to be converted to a string.

Caution: In the Subject field, three percent signs (%%%) are placed before and after the functions and field names. If you type a function or field name directly in the Subject field, you must type three percent signs before and after it. If you use Expression Builder to embed a function or field name, the percent signs are automatically added and must not be pasted into Expression Builder. When percent signs are pasted into Expression Builder, Expression Builder displays an internal error.

For more information about expressions, see Oracle CRM On Demand Online Help.

Enter the following expression in the Subject field:

%%%LookupValue("TODO_TYPE", "Birthday Call")%%%-%%%JoinFieldValue('<Lead>',[<LeadId>],
'<LeadFullName>')%%%

Followup Calls for Birthday Calls Where the Result Is Stay in Touch and the Birthday Is Within Six Months

This workflow rule is triggered when a producer calls a lead or client through a birthday call and then updates the Call Result field in the Task edit page to Stay in Touch. If the birthday of the lead or client is more than six months away, the workflow rule creates a review call followup task to call the lead or client six months from now.

Note: The expressions in this topic might appear across several lines due to length. All expressions in this topic must be entered in Expression Builder as one line and cannot contain any spaces. Also, the language-independent field names and the field-name syntax used in the expressions in this topic are the field names and syntax that were used in Expression Builder in releases earlier than Release 29 Service Pack 1. These expressions are still valid in Release 29 Service Pack 1 and later releases. However, starting with Release 29 Service Pack 1, Expression Builder uses language-independent field names and a field-name syntax that are different from the field names and the field-name syntax used in earlier releases. So, if you select the corresponding fields from the field list in Expression Builder when you create or update an expression in Release 29 Service Pack 1 or a later release, then the field names in the expression will be different from the field names shown in this topic, and the fields will appear in the expression editor with the following syntax: [{FieldName}]. It is recommended that you always select the fields for your expressions from the list of fields in Expression Builder, so that the field names and the field syntax are always correct. For more information about Expression Builder, see Oracle CRM On Demand Online Help.

Workflow Rule Details

This topic describes the details of the workflow rule.

Record Type

The record type is an Activity record.

Trigger Event

The trigger event is When Modified Record Saved.

Rule Condition

The Workflow Rule Condition field contains the workflow rule condition.

Enter the following expression in the Workflow Rule Condition field:

[<Type>]=LookupValue("TODO_TYPE", "Birthday Call") AND [<CallResult>]=LookupValue("OD_CALL_RESULT", 
"Stay In Touch") AND PRE('<CallResult>') IS NULL AND ([<PrimaryContactId>] <> "No Match Row Id" OR 
[<LeadId>] <> "No Match Row Id")

Workflow Action Details

This topic describes the details of the workflow action.

Action Type

The action type is Create Task.

Task Type

The task type is a Review Call.

Due Date

The Due Date field contains a numeric value that is calculated by adding the value in this field to the date on which the task is created.

Enter the following expression in the Due Date field:

IIf((IfNull(Mid(1.0 * JulianDay(Today()+Duration("P6M"))/7, 8, 1), "0")>="7"),IIf((IfNull(Mid
(1.0 * JulianDay(Today()+Duration("P6M"))/7, 8, 1), "0")="7"),Today()+Duration("P6M")+2,Today()
+Duration("P6M")+1),Today()+Duration("P6M"))

Subject

The Subject field contains the subject line for the task. You can embed functions and field names in the text. Three percent signs (%%%) before and after an embedded function or field name indicate that it is to be converted to a string.

Caution: In the Subject field, three percent signs (%%%) are placed before and after the functions and field names. If you type a function or field name directly in the Subject field, you must type three percent signs before and after it. If you use Expression Builder to embed a function or field name, the percent signs are automatically added and must not be pasted into Expression Builder. When percent signs are pasted into Expression Builder, Expression Builder displays an internal error.

For more information about expressions, see Oracle CRM On Demand Online Help.

Enter the following expression in the Subject field:

%%%LookupValue("TODO_TYPE", "Review Call")%%%-%%%IIf([<PrimaryContactId>] <> "No Match Row Id",
JoinFieldValue('<Contact>',[<PrimaryContactId>],'<ContactFullName>'),JoinFieldValue('<Lead>',
[<LeadId>],'<LeadFullName>'))%%%

Followup Calls for Review Calls where the Result is Stay in Touch and the Birthday is Within the Current Week or Unknown

This workflow rule is triggered when a producer calls a lead or client through a review call and then updates the Call Result field in the Task edit page to Stay in Touch. If the birthday of the lead or client is not known or the birthday is within the current week, the workflow rule creates a review call followup task to call the lead or client six months from now.

Note: The expressions in this topic might appear across several lines due to length. All expressions in this topic must be entered in Expression Builder as one line and cannot contain any spaces. Also, the language-independent field names and the field-name syntax used in the expressions in this topic are the field names and syntax that were used in Expression Builder in releases earlier than Release 29 Service Pack 1. These expressions are still valid in Release 29 Service Pack 1 and later releases. However, starting with Release 29 Service Pack 1, Expression Builder uses language-independent field names and a field-name syntax that are different from the field names and the field-name syntax used in earlier releases. So, if you select the corresponding fields from the field list in Expression Builder when you create or update an expression in Release 29 Service Pack 1 or a later release, then the field names in the expression will be different from the field names shown in this topic, and the fields will appear in the expression editor with the following syntax: [{FieldName}]. It is recommended that you always select the fields for your expressions from the list of fields in Expression Builder, so that the field names and the field syntax are always correct. For more information about Expression Builder, see Oracle CRM On Demand Online Help.

Workflow Rule Details

This topic describes the details of the workflow rule.

Record Type

The record type is an Activity record.

Trigger Event

The trigger event is When Modified Record Saved.

Rule Condition

The Workflow Rule Condition field contains the workflow rule condition.

Enter the following expression in the Workflow Rule Condition field:

([<Type>]=LookupValue("TODO_TYPE","Review Call") OR [<Type>]=LookupValue("TODO_TYPE","Referral 
Call")) AND [<PrimaryContactId>] = "No Match Row Id" AND [<CallResult>]=LookupValue("OD_CALL_RESULT", 
"Stay In Touch") AND PRE('<CallResult>') IS NULL AND IIf(JoinFieldValue('<Lead>',[<LeadId>],
'<DateofBirth>') IS NOT NULL,(JulianDay(IIf(JulianDay(Mid(JoinFieldValue('<Lead>',[<LeadId>],
'<DateofBirth>'),1,6)+ToChar(Today(),'YYYY'))<JulianDay(Today()),Mid(JoinFieldValue('<Lead>',
[<LeadId>],'<DateofBirth>'),1,6)+ToChar(Today()+Duration("P1Y"),'YYYY'), Mid(JoinFieldValue
('<Lead>',[<LeadId>],'<DateofBirth>'),1,6)+ToChar(Today(),'YYYY')))<=JulianDay(Today()+7)),
[<LeadId>]<>"No Match Row Id")

Workflow Action Details

This topic describes the details of the workflow action.

Action Type

The action type is Create Task.

Task Type

The task type is a Review Call.

Due Date

The Due Date field contains a numeric value that is calculated by adding the value in this field to the date on which the task is created.

Enter the following expression in the Due Date field:

IIf((IfNull(Mid(1.0 * JulianDay(Today()+Duration("P6M"))/7, 8, 1), "0")>="7"),IIf((IfNull(Mid
(1.0 * JulianDay(Today()+Duration("P6M"))/7, 8, 1), "0")="7"),Today()+Duration("P6M")+2,Today()
+Duration("P6M")+1),Today()+Duration("P6M"))

Subject

The Subject field contains the subject line for the task. You can embed functions and field names in the text. Three percent signs (%%%) before and after an embedded function or field name indicate that it is to be converted to a string.

Caution: In the Subject field, three percent signs (%%%) are placed before and after the functions and field names. If you type a function or field name directly in the Subject field, you must type three percent signs before and after it. If you use Expression Builder to embed a function or field name, the percent signs are automatically added and must not be pasted into Expression Builder. When percent signs are pasted into Expression Builder, Expression Builder displays an internal error.

For more information about expressions, see Oracle CRM On Demand Online Help.

Enter the following expression in the Subject field:

%%%LookupValue("TODO_TYPE", "Review Call")%%%-%%%JoinFieldValue('<Lead>',[<LeadId>],
'<LeadFullName>')%%%

Followup Calls for Review Calls Where the Result Is Stay in Touch and the Birthday Is Not Within Six Months

This workflow rule is triggered when a producer calls a lead or client through a review call and then updates the Call Result field in the Task edit page to Stay in Touch. If the birthday of the lead or client is more than six months from now, the workflow rule creates a review call followup task to call the lead or client six months from now.

Note: The expressions in this topic might appear across several lines due to length. All expressions in this topic must be entered in Expression Builder as one line and cannot contain any spaces. Also, the language-independent field names and the field-name syntax used in the expressions in this topic are the field names and syntax that were used in Expression Builder in releases earlier than Release 29 Service Pack 1. These expressions are still valid in Release 29 Service Pack 1 and later releases. However, starting with Release 29 Service Pack 1, Expression Builder uses language-independent field names and a field-name syntax that are different from the field names and the field-name syntax used in earlier releases. So, if you select the corresponding fields from the field list in Expression Builder when you create or update an expression in Release 29 Service Pack 1 or a later release, then the field names in the expression will be different from the field names shown in this topic, and the fields will appear in the expression editor with the following syntax: [{FieldName}]. It is recommended that you always select the fields for your expressions from the list of fields in Expression Builder, so that the field names and the field syntax are always correct. For more information about Expression Builder, see Oracle CRM On Demand Online Help.

Workflow Rule Details

This topic describes the details of the workflow rule.

Record Type

The record type is an Activity record.

Trigger Event

The trigger event is When Modified Record Saved.

Rule Condition

The Workflow Rule Condition field contains the workflow rule condition.

Enter the following expression in the Workflow Rule Condition field:

([<Type>]=LookupValue("TODO_TYPE","Review Call") OR [<Type>]=LookupValue("TODO_TYPE",
"Referral Call")) AND [<PrimaryContactId>] = "No Match Row Id" AND [<CallResult>]=LookupValue
("OD_CALL_RESULT", "Stay In Touch") AND PRE('<CallResult>') IS NULL AND JoinFieldValue('<Lead>',
[<LeadId>],'<DateofBirth>') IS NOT NULL AND JulianDay(IIf(JulianDay(Mid(JoinFieldValue('<Lead>',
[<LeadId>],'<DateofBirth>'),1,6)+ToChar(Today(),'YYYY'))<JulianDay(Today()),Mid(JoinFieldValue
('<Lead>',[<LeadId>],'<DateofBirth>'),1,6)+ToChar(Today()+Duration("P1Y"),'YYYY'), 
Mid(JoinFieldValue('<Lead>',[<LeadId>],'<DateofBirth>'),1,6)+ToChar(Today(),'YYYY')))>JulianDay
(Today()+Duration("P6M"))

Workflow Action Details

This topic describes the details of the workflow action.

Action Type

The action type is Create Task.

Task Type

The task type is a Review Call.

Due Date

The Due Date field contains a numeric value that is calculated by adding the value in this field to the date on which the task is created.

Enter the following expression in the Due Date field:

IIf((IfNull(Mid(1.0 * JulianDay(Today()+Duration("P6M"))/7, 8, 1), "0")>="7"),IIf((IfNull(Mid
(1.0 * JulianDay(Today()+Duration("P6M"))/7, 8, 1), "0")="7"),Today()+Duration("P6M")+2,Today()
+Duration("P6M")+1),Today()+Duration("P6M"))

Subject

The Subject field contains the subject line for the task. You can embed functions and field names in the text. Three percent signs (%%%) before and after an embedded function or field name indicate that it is to be converted to a string.

Caution: In the Subject field, three percent signs (%%%) are placed before and after the functions and field names. If you type a function or field name directly in the Subject field, you must type three percent signs before and after it. If you use Expression Builder to embed a function or field name, the percent signs are automatically added and must not be pasted into Expression Builder. When percent signs are pasted into Expression Builder, Expression Builder displays an internal error.

For more information about expressions, see Oracle CRM On Demand Online Help.

Enter the following expression in the Subject field:

%%%LookupValue("TODO_TYPE", "Review Call")%%%-%%%JoinFieldValue('<Lead>',[<LeadId>],
'<LeadFullName>')%%%

Followup Calls for Review Calls Where the Result Is Stay in Touch and the Birthday Is Not in the Current Week and Within Six Months

This workflow rule is triggered when a producer calls a lead or client through a review call and then updates the Call Result field in the Task edit page to Stay in Touch. If the birthday of the lead or client is not in the current week and is not more than six months from now, the workflow rule creates a review call followup task to call the lead or client a week before the birthday.

Note: The expressions in this topic might appear across several lines due to length. All expressions in this topic must be entered in Expression Builder as one line and cannot contain any spaces. Also, the language-independent field names and the field-name syntax used in the expressions in this topic are the field names and syntax that were used in Expression Builder in releases earlier than Release 29 Service Pack 1. These expressions are still valid in Release 29 Service Pack 1 and later releases. However, starting with Release 29 Service Pack 1, Expression Builder uses language-independent field names and a field-name syntax that are different from the field names and the field-name syntax used in earlier releases. So, if you select the corresponding fields from the field list in Expression Builder when you create or update an expression in Release 29 Service Pack 1 or a later release, then the field names in the expression will be different from the field names shown in this topic, and the fields will appear in the expression editor with the following syntax: [{FieldName}]. It is recommended that you always select the fields for your expressions from the list of fields in Expression Builder, so that the field names and the field syntax are always correct. For more information about Expression Builder, see Oracle CRM On Demand Online Help.

Workflow Rule Details

This topic describes the details of the workflow rule.

Record Type

The record type is an Activity record.

Trigger Event

The trigger event is When Modified Record Saved.

Rule Condition

The Workflow Rule Condition field contains the workflow rule condition.

Enter the following expression in the Workflow Rule Condition field:

[<Type>]=LookupValue("TODO_TYPE", "Review Call") AND [<CallResult>]=LookupValue("OD_CALL_RESULT", 
"Stay In Touch") AND PRE('<CallResult>') IS NULL AND JoinFieldValue('<Contact>',
[<PrimaryContactId>],'<DateofBirth>') IS NOT NULL AND JulianDay(IIf(JulianDay(Mid(JoinFieldValue
('<Contact>',[<PrimaryContactId>],'<DateofBirth>'),1,6)+ToChar(Today(),'YYYY')) < JulianDay
(Today()),Mid(JoinFieldValue('<Contact>',[<PrimaryContactId>],'<DateofBirth>'),1,6)+ToChar(Today()
+Duration("P1Y"),'YYYY'), Mid(JoinFieldValue('<Contact>',[<PrimaryContactId>],'<DateofBirth>'),1,6)
+ToChar(Today(),'YYYY')))>JulianDay(Today()+7) AND JulianDay(IIf(JulianDay(Mid(JoinFieldValue
('<Contact>',[<PrimaryContactId>],'<DateofBirth>'),1,6)+ToChar(Today(),'YYYY')) < JulianDay
(Today()),Mid(JoinFieldValue('<Contact>',[<PrimaryContactId>],'<DateofBirth>'),1,6)+ToChar
(Today()+Duration("P1Y"),'YYYY'), Mid(JoinFieldValue('<Contact>',[<PrimaryContactId>],
'<DateofBirth>'),1,6)+ToChar(Today(),'YYYY')))<=JulianDay(Today()+Duration("P6M"))

Workflow Action Details

This topic describes the details of the workflow action.

Action Type

The action type is Create Task.

Task Type

The task type is a Birthday Call.

Due Date

The Due Date field contains a numeric value that is calculated by adding the value in this field to the date on which the task is created.

Enter the following expression in the Due Date field:

Today()+JulianDay(Mid(JoinFieldValue('<Contact>',[<PrimaryContactId>],'<DateofBirth>'),1,6)+IIf
(JulianDay(Mid(JoinFieldValue('<Contact>',[<PrimaryContactId>],'<DateofBirth>'),1,6)+ToChar
(Today(),'YYYY')) < JulianDay(Today()),ToChar(Today()+Duration("P1Y"),'YYYY'),ToChar(Today(),
'YYYY')))-JulianDay(Today())-(IIf(IfNull(Mid(1.0*(JulianDay(Mid(JoinFieldValue('<Contact>',
[<PrimaryContactId>],'<DateofBirth>'),1,6)+IIf(JulianDay(Mid(JoinFieldValue('<Contact>',
[<PrimaryContactId>],'<DateofBirth>'),1,6)+ToChar(Today(),'YYYY')) < JulianDay(Today()),
ToChar(Today()+Duration("P1Y"),'YYYY'),ToChar(Today(),'YYYY')))-7)/7,8,1),"0")>="7",(IIf
(IfNull(Mid(1.0*(JulianDay(Mid(JoinFieldValue('<Contact>',[<PrimaryContactId>],'<DateofBirth>'),
1,6)+IIf(JulianDay(Mid(JoinFieldValue('<Contact>',[<PrimaryContactId>],'<DateofBirth>'),1,6)
+ToChar(Today(),'YYYY')) < JulianDay(Today()),ToChar(Today()+Duration("P1Y"),'YYYY'),ToChar
(Today(),'YYYY')))-7)/7,8,1),"0")="7",5,6)),7))

Subject

The Subject field contains the subject line for the task. You can embed functions and field names in the text. Three percent signs (%%%) before and after an embedded function or field name indicate that it is to be converted to a string.

Caution: In the Subject field, three percent signs (%%%) are placed before and after the functions and field names. If you type a function or field name directly in the Subject field, you must type three percent signs before and after it. If you use Expression Builder to embed a function or field name, the percent signs are automatically added and must not be pasted into Expression Builder. When percent signs are pasted into Expression Builder, Expression Builder displays an internal error.

For more information about expressions, see Oracle CRM On Demand Online Help.

Enter the following expression in the Subject field:

%%%LookupValue("TODO_TYPE", "Birthday Call")%%%-%%%JoinFieldValue('<Contact>',[<PrimaryContactId>],
'<ContactFullName>')%%%

Followup Calls for Review Calls Where the Result Is Stay in Touch and the Birthday Is Not in the Current Week or Is Unknown

This workflow rule is triggered when a producer calls a lead or client through a review call and then updates the Call Result field in the Task edit page to Stay in Touch. If the birthday of the lead or client is not in the current week or the birthday is not known, the workflow rule creates a Review Call followup task to call the lead or client six months from now.

Note: The expressions in this topic might appear across several lines due to length. All expressions in this topic must be entered in Expression Builder as one line and cannot contain any spaces. Also, the language-independent field names and the field-name syntax used in the expressions in this topic are the field names and syntax that were used in Expression Builder in releases earlier than Release 29 Service Pack 1. These expressions are still valid in Release 29 Service Pack 1 and later releases. However, starting with Release 29 Service Pack 1, Expression Builder uses language-independent field names and a field-name syntax that are different from the field names and the field-name syntax used in earlier releases. So, if you select the corresponding fields from the field list in Expression Builder when you create or update an expression in Release 29 Service Pack 1 or a later release, then the field names in the expression will be different from the field names shown in this topic, and the fields will appear in the expression editor with the following syntax: [{FieldName}]. It is recommended that you always select the fields for your expressions from the list of fields in Expression Builder, so that the field names and the field syntax are always correct. For more information about Expression Builder, see Oracle CRM On Demand Online Help.

Workflow Rule Details

This topic describes the details of the workflow rule.

Record Type

The record type is an Activity record.

Trigger Event

The trigger event is When Modified Record Saved.

Rule Condition

The Workflow Rule Condition field contains the workflow rule condition.

Enter the following expression in the Workflow Rule Condition field:

[<Type>]=LookupValue("TODO_TYPE","Review Call") AND [<CallResult>]=LookupValue("OD_CALL_RESULT",
"Stay In Touch") AND PRE('<CallResult>') IS NULL AND IIf(JoinFieldValue('<Contact>',
[<PrimaryContactId>],'<DateofBirth>') IS NOT NULL,JulianDay(IIf(JulianDay(Mid(JoinFieldValue
('<Contact>',[<PrimaryContactId>],'<DateofBirth>'),1,6)+ToChar(Today(),'YYYY'))<JulianDay
(Today()),Mid(JoinFieldValue('<Contact>',[<PrimaryContactId>],'<DateofBirth>'),1,6)+ToChar
(Today()+Duration("P1Y"),'YYYY'),Mid(JoinFieldValue('<Contact>',[<PrimaryContactId>],
'<DateofBirth>'),1,6)+ToChar(Today(),'YYYY')))<=JulianDay(Today()+7),[<PrimaryContactId>]<>"No 
Match Row Id")

Workflow Action Details

This topic describes the details of the workflow action.

Action Type

The action type is Create Task.

Task Type

The task type is a Review Call.

Due Date

The Due Date field contains a numeric value that is calculated by adding the value in this field to the date on which the task is created.

Enter the following expression in the Due Date field:

IIf((IfNull(Mid(1.0 * JulianDay(Today()+Duration("P6M"))/7, 8, 1), "0")>="7"),IIf((IfNull(Mid
(1.0 * JulianDay(Today()+Duration("P6M"))/7, 8, 1), "0")="7"),Today()+Duration("P6M")+2,Today()
+Duration("P6M")+1),Today()+Duration("P6M"))

Subject

The Subject field contains the subject line for the task. You can embed functions and field names in the text. Three percent signs (%%%) before and after an embedded function or field name indicate that it is to be converted to a string.

Caution: In the Subject field, three percent signs (%%%) are placed before and after the functions and field names. If you type a function or field name directly in the Subject field, you must type three percent signs before and after it. If you use Expression Builder to embed a function or field name, the percent signs are automatically added and must not be pasted into Expression Builder. When percent signs are pasted into Expression Builder, Expression Builder displays an internal error.

For more information about expressions, see Oracle CRM On Demand Online Help.

Enter the following expression in the Subject field:

%%%LookupValue("TODO_TYPE", "Review Call")%%%-%%%JoinFieldValue('<Contact>',[<PrimaryContactId>],
'<ContactFullName>')%%%

Followup Calls for Review Calls Where the Result Is Stay in Touch and the Birthday Is Not Within Six Months

This workflow rule is triggered when a producer calls a lead or client through a review call and then updates the Call Result field in the Task edit page to Stay in Touch. If the birthday of the lead or client more than six months from now, the workflow rule creates a review call followup task to call the lead or client six months from now.

Note: The expressions in this topic might appear across several lines due to length. All expressions in this topic must be entered in Expression Builder as one line and cannot contain any spaces. Also, the language-independent field names and the field-name syntax used in the expressions in this topic are the field names and syntax that were used in Expression Builder in releases earlier than Release 29 Service Pack 1. These expressions are still valid in Release 29 Service Pack 1 and later releases. However, starting with Release 29 Service Pack 1, Expression Builder uses language-independent field names and a field-name syntax that are different from the field names and the field-name syntax used in earlier releases. So, if you select the corresponding fields from the field list in Expression Builder when you create or update an expression in Release 29 Service Pack 1 or a later release, then the field names in the expression will be different from the field names shown in this topic, and the fields will appear in the expression editor with the following syntax: [{FieldName}]. It is recommended that you always select the fields for your expressions from the list of fields in Expression Builder, so that the field names and the field syntax are always correct. For more information about Expression Builder, see Oracle CRM On Demand Online Help.

Workflow Rule Details

This topic describes the details of the workflow rule.

Record Type

The record type is an Activity record.

Trigger Event

The trigger event is When Modified Record Saved.

Rule Condition

The Workflow Rule Condition field contains the workflow rule condition.

Enter the following expression in the Workflow Rule Condition field:

[<Type>]=LookupValue("TODO_TYPE","Review Call") AND [<CallResult>]=LookupValue("OD_CALL_RESULT",
"Stay In Touch") AND PRE('<CallResult>') IS NULL AND JoinFieldValue('<Contact>',[<PrimaryContactId>],
'<DateofBirth>') IS NOT NULL AND JulianDay(IIf(JulianDay(Mid(JoinFieldValue('<Contact>',
[<PrimaryContactId>],'<DateofBirth>'),1,6)+ToChar(Today(),'YYYY'))<JulianDay(Today()),Mid
(JoinFieldValue('<Contact>',[<PrimaryContactId>],'<DateofBirth>'),1,6)+ToChar(Today()+Duration
("P1Y"),'YYYY'),Mid(JoinFieldValue('<Contact>',[<PrimaryContactId>],'<DateofBirth>'),1,6)+ToChar
(Today(),'YYYY')))>JulianDay(Today()+Duration("P6M"))

Workflow Action Details

This topic describes the details of the workflow action.

Action Type

The action type is Create Task.

Task Type

The task type is a Review Call.

Due Date

The Due Date field contains a numeric value that is calculated by adding the value in this field to the date on which the task is created.

Enter the following expression in the Due Date field:

IIf((IfNull(Mid(1.0 * JulianDay(Today()+Duration("P6M"))/7, 8, 1), "0")>="7"),IIf((IfNull(Mid
(1.0 * JulianDay(Today()+Duration("P6M"))/7, 8, 1), "0")="7"),Today()+Duration("P6M")+2,Today()
+Duration("P6M")+1),Today()+Duration("P6M"))

Subject

The Subject field contains the subject line for the task. You can embed functions and field names in the text. Three percent signs (%%%) before and after an embedded function or field name indicate that it is to be converted to a string.

Caution: In the Subject field, three percent signs (%%%) are placed before and after the functions and field names. If you type a function or field name directly in the Subject field, you must type three percent signs before and after it. If you use Expression Builder to embed a function or field name, the percent signs are automatically added and must not be pasted into Expression Builder. When percent signs are pasted into Expression Builder, Expression Builder displays an internal error.

For more information about expressions, see Oracle CRM On Demand Online Help.

Enter the following expression in the Subject field:

%%%LookupValue("TODO_TYPE", "Review Call")%%%-%%%JoinFieldValue('<Contact>',[<PrimaryContactId>],
'<ContactFullName>')%%%

Workflow Rules for Scheduling Calls with Clients

When a lead decides to purchase a product, the producer converts the lead to a contact and sets the contact type field to Client. The producer must keep in regular touch with the new client by having review calls or birthday calls scheduled for the client. When the producer creates the contact record for the client, the producer sets the Call Frequency field to 1-2 Times/Year. When the Call Frequency field is updated, the following workflow rules create a Review Call or Birthday Call followup task to call the client either six months from now or one week before the birthday, whichever occurs first.

Schedule Calls with Clients Where the Birthday Is Not in the Current Week and Is Within Six Months

This workflow rule is triggered when a producer updates the Call Frequency field on the contact (client) record to 1-2 Times/Year. If the birthday of the client is not within the current week and is not more than six months from now, the workflow rule creates a birthday call task to call the client a week before the birthday.

Note: The expressions in this topic might appear across several lines due to length. All expressions in this topic must be entered in Expression Builder as one line and cannot contain any spaces. Also, the language-independent field names and the field-name syntax used in the expressions in this topic are the field names and syntax that were used in Expression Builder in releases earlier than Release 29 Service Pack 1. These expressions are still valid in Release 29 Service Pack 1 and later releases. However, starting with Release 29 Service Pack 1, Expression Builder uses language-independent field names and a field-name syntax that are different from the field names and the field-name syntax used in earlier releases. So, if you select the corresponding fields from the field list in Expression Builder when you create or update an expression in Release 29 Service Pack 1 or a later release, then the field names in the expression will be different from the field names shown in this topic, and the fields will appear in the expression editor with the following syntax: [{FieldName}]. It is recommended that you always select the fields for your expressions from the list of fields in Expression Builder, so that the field names and the field syntax are always correct. For more information about Expression Builder, see Oracle CRM On Demand Online Help.

Workflow Rule Details

This topic describes the details of the workflow rule.

Record Type

The record type is a Contact record.

Trigger Event

The trigger event is When Modified Record Saved.

Rule Condition

The Workflow Rule Condition field contains the workflow rule condition.

Enter the following expression in the Workflow Rule Condition field:

[<CallFrequency>] <> IfNull(PRE('<CallFrequency>'),"Invalid") AND [<CallFrequency>]=LookupValue
('PROF_CALL_CLASS','1-2 Times/Year') AND [<DateofBirth>] IS NOT NULL AND (JulianDay(IIf
(JulianDay(Mid([<DateofBirth>], 1, 6) + ToChar(Today(), 'YYYY')) < JulianDay(Today()), Mid(
[<DateofBirth>], 1, 6) + ToChar(Today()+Duration("P1Y"),'YYYY'),Mid([<DateofBirth>],1, 6) 
+ ToChar(Today(), 'YYYY'))) <= JulianDay(Today()+Duration("P6M"))) AND (JulianDay(IIf(JulianDay
(Mid([<DateofBirth>], 1, 6) + ToChar(Today(), 'YYYY')) < JulianDay(Today()), Mid([<DateofBirth>], 
1, 6) + ToChar(Today()+Duration("P1Y"),'YYYY'),Mid([<DateofBirth>],1, 6) + ToChar(Today(), 
'YYYY'))) > JulianDay(Today()+7))

Workflow Action Details

This topic describes the details of the workflow action.

Action Type

The action type is Create Task.

Task Type

The task type is a Birthday Call.

Due Date

The Due Date field contains a numeric value that is calculated by adding the value in this field to the date on which the task is created.

Enter the following expression in the Due Date field:

Today()+JulianDay(Mid([<DateofBirth>],1,6)+IIf(JulianDay(Mid([<DateofBirth>],1,6)+ToChar(Today(),
'YYYY')) < JulianDay(Today()),ToChar(Today()+Duration("P1Y"),'YYYY'),ToChar(Today(),'YYYY')))
-JulianDay(Today())-(IIf(IfNull(Mid(1.0*(JulianDay(Mid([<DateofBirth>],1,6)+IIf(JulianDay(Mid
([<DateofBirth>],1,6)+ToChar(Today(),'YYYY')) < JulianDay(Today()),ToChar(Today()+Duration
("P1Y"),'YYYY'),ToChar(Today(),'YYYY')))-7)/7,8,1),"0")>="7",(IIf(IfNull(Mid(1.0*(JulianDay(Mid
([<DateofBirth>],1,6)+IIf(JulianDay(Mid([<DateofBirth>],1,6)+ToChar(Today(),'YYYY')) < JulianDay
(Today()),ToChar(Today()+Duration("P1Y"),'YYYY'),ToChar(Today(),'YYYY')))-7)/7,8,1),"0")="7",5,6)),7))

Subject

The Subject field contains the subject line for the task. You can embed functions and field names in the text. Three percent signs (%%%) before and after an embedded function or field name indicate that it is to be converted to a string.

Caution: In the Subject field, three percent signs (%%%) are placed before and after the functions and field names. If you type a function or field name directly in the Subject field, you must type three percent signs before and after it. If you use Expression Builder to embed a function or field name, the percent signs are automatically added and must not be pasted into Expression Builder. When percent signs are pasted into Expression Builder, Expression Builder displays an internal error.

For more information about expressions, see Oracle CRM On Demand Online Help.

Enter the following expression in the Subject field:

%%%LookupValue("TODO_TYPE", "Birthday Call")%%%-%%%FieldValue('<ContactFullName>')%%%

Schedule Calls with Clients Where the Birthday Is Unknown, Is in the Current Week, or Is Not Within Six Months

This workflow rule is triggered when a producer updates the Call Frequency field on the contact (client) record to 1-2 Times/Year. If the birthday of the client is not known, or is within the current week, or is more than six months from now, the workflow rule creates a review call task to call the contact six months from now.

Note: The expressions in this topic might appear across several lines due to length. All expressions in this topic must be entered in Expression Builder as one line and cannot contain any spaces. Also, the language-independent field names and the field-name syntax used in the expressions in this topic are the field names and syntax that were used in Expression Builder in releases earlier than Release 29 Service Pack 1. These expressions are still valid in Release 29 Service Pack 1 and later releases. However, starting with Release 29 Service Pack 1, Expression Builder uses language-independent field names and a field-name syntax that are different from the field names and the field-name syntax used in earlier releases. So, if you select the corresponding fields from the field list in Expression Builder when you create or update an expression in Release 29 Service Pack 1 or a later release, then the field names in the expression will be different from the field names shown in this topic, and the fields will appear in the expression editor with the following syntax: [{FieldName}]. It is recommended that you always select the fields for your expressions from the list of fields in Expression Builder, so that the field names and the field syntax are always correct. For more information about Expression Builder, see Oracle CRM On Demand Online Help.

Workflow Rule Details

This topic describes the details of the workflow rule.

Record Type

The record type is a Contact record.

Trigger Event

The trigger event is When Modified Record Saved.

Rule Condition

The Workflow Rule Condition field contains the workflow rule condition.

Enter the following expression in the Workflow Rule Condition field:

[<CallFrequency>] <> IfNull(PRE('<CallFrequency>'),"Invalid") AND [<CallFrequency>]=LookupValue
('PROF_CALL_CLASS','1-2 Times/Year') AND IIf([<DateofBirth>] IS NOT NULL, ((JulianDay(IIf(JulianDay
(Mid([<DateofBirth>], 1, 6) + ToChar(Today(), 'YYYY')) < JulianDay(Today()), Mid([<DateofBirth>], 
1, 6) + ToChar(Today()+Duration("P1Y"),'YYYY'),Mid([<DateofBirth>],1, 6) + ToChar(Today(), 
'YYYY'))) > JulianDay(Today()+Duration("P6M"))) OR (JulianDay(IIf(JulianDay(Mid([<DateofBirth>], 
1, 6) + ToChar(Today(), 'YYYY')) < JulianDay(Today()), Mid([<DateofBirth>],1,6) + ToChar(Today()
+Duration("P1Y"),'YYYY'),Mid([<DateofBirth>],1, 6) + ToChar(Today(), 'YYYY'))) <= JulianDay
(Today()+7))),1)

Workflow Action Details

This topic describes the details of the workflow action.

Action Type

The action type is Create Task.

Task Type

The task type is a Review Call.

Due Date

The Due Date field contains a numeric value that is calculated by adding the value in this field to the date on which the task is created.

Enter the following expression in the Due Date field:

IIf((IfNull(Mid(1.0 * JulianDay(Today()+Duration("P6M"))/7, 8, 1), "0")>="7"),IIf((IfNull(Mid
(1.0 * JulianDay(Today()+Duration("P6M"))/7, 8, 1), "0")="7"),Today()+Duration("P6M")+2,Today()
+Duration("P6M")+1),Today()+Duration("P6M"))

Subject

The Subject field contains the subject line for the task. You can embed functions and field names in the text. Three percent signs (%%%) before and after an embedded function or field name indicate that it is to be converted to a string.

Caution: In the Subject field, three percent signs (%%%) are placed before and after the functions and field names. If you type a function or field name directly in the Subject field, you must type three percent signs before and after it. If you use Expression Builder to embed a function or field name, the percent signs are automatically added and must not be pasted into Expression Builder. When percent signs are pasted into Expression Builder, Expression Builder displays an internal error.

For more information about expressions, see Oracle CRM On Demand Online Help.

Enter the following expression in the Subject field:

%%%LookupValue("TODO_TYPE", "Review Call")%%%- %%%FieldValue('<ContactFullName>')%%%

Schedule Calls with Clients Where the Birthday Is Within Six Months and Is Not in the Current Week

This workflow rule is triggered when a producer updates the Call Frequency field on the contact (client) record to 1-2 Times/Year. If the birthday of the client is not more than six months from now and is not within the current week, the workflow rule creates a birthday call task to call the client one week before the birthday.

Note: The expressions in this topic might appear across several lines due to length. All expressions in this topic must be entered in Expression Builder as one line and cannot contain any spaces. Also, the language-independent field names and the field-name syntax used in the expressions in this topic are the field names and syntax that were used in Expression Builder in releases earlier than Release 29 Service Pack 1. These expressions are still valid in Release 29 Service Pack 1 and later releases. However, starting with Release 29 Service Pack 1, Expression Builder uses language-independent field names and a field-name syntax that are different from the field names and the field-name syntax used in earlier releases. So, if you select the corresponding fields from the field list in Expression Builder when you create or update an expression in Release 29 Service Pack 1 or a later release, then the field names in the expression will be different from the field names shown in this topic, and the fields will appear in the expression editor with the following syntax: [{FieldName}]. It is recommended that you always select the fields for your expressions from the list of fields in Expression Builder, so that the field names and the field syntax are always correct. For more information about Expression Builder, see Oracle CRM On Demand Online Help.

Workflow Rule Details

This topic describes the details of the workflow rule.

Record Type

The record type is a Contact record.

Trigger Event

The trigger event is When New Record Saved.

Rule Condition

The Workflow Rule Condition field contains the workflow rule condition.

Enter the following expression in the Workflow Rule Condition field:

[<CallFrequency>]=LookupValue('PROF_CALL_CLASS','1-2 Times/Year') AND [<DateofBirth>] IS NOT 
NULL AND (JulianDay(IIf(JulianDay(Mid([<DateofBirth>], 1, 6) + ToChar(Today(), 'YYYY')) 
< JulianDay(Today()), Mid([<DateofBirth>], 1, 6) + ToChar(Today()+Duration("P1Y"),'YYYY'),Mid
([<DateofBirth>],1, 6) + ToChar(Today(), 'YYYY'))) <= JulianDay(Today()+Duration("P6M"))) AND 
(JulianDay(IIf(JulianDay(Mid([<DateofBirth>], 1, 6) + ToChar(Today(), 'YYYY')) < JulianDay
(Today()), Mid([<DateofBirth>], 1, 6) + ToChar(Today()+Duration("P1Y"),'YYYY'),Mid(
[<DateofBirth>],1, 6) + ToChar(Today(), 'YYYY'))) > JulianDay(Today()+7))

Workflow Action Details

This topic describes the details of the workflow action.

Action Type

The action type is Create Task.

Task Type

The task type is a Birthday Call.

Due Date

The Due Date field contains a numeric value that is calculated by adding the value in this field to the date on which the task is created.

Enter the following expression in the Due Date field:

Today()+JulianDay(Mid([<DateofBirth>],1,6)+IIf(JulianDay(Mid([<DateofBirth>],1,6)+ToChar(Today(),
'YYYY')) < JulianDay(Today()),ToChar(Today()+Duration("P1Y"),'YYYY'),ToChar(Today(),'YYYY')))
-JulianDay(Today())-(IIf(IfNull(Mid(1.0*(JulianDay(Mid([<DateofBirth>],1,6)+IIf(JulianDay(Mid(
[<DateofBirth>],1,6)+ToChar(Today(),'YYYY')) < JulianDay(Today()),ToChar(Today()+Duration("P1Y"),
'YYYY'),ToChar(Today(),'YYYY')))-7)/7,8,1),"0")>="7",(IIf(IfNull(Mid(1.0*(JulianDay(Mid(
[<DateofBirth>],1,6)+IIf(JulianDay(Mid([<DateofBirth>],1,6)+ToChar(Today(),'YYYY')) < 
JulianDay(Today()),ToChar(Today()+Duration("P1Y"),'YYYY'),ToChar(Today(),'YYYY')))-7)/7,8,1),
"0")="7",5,6)),7))

Subject

The Subject field contains the subject line for the task. You can embed functions and field names in the text. Three percent signs (%%%) before and after an embedded function or field name indicate that it is to be converted to a string.

Caution: In the Subject field, three percent signs (%%%) are placed before and after the functions and field names. If you type a function or field name directly in the Subject field, you must type three percent signs before and after it. If you use Expression Builder to embed a function or field name, the percent signs are automatically added and must not be pasted into Expression Builder. When percent signs are pasted into Expression Builder, Expression Builder displays an internal error.

For more information about expressions, see Oracle CRM On Demand Online Help.

Enter the following expression in the Subject field:

%%%LookupValue("TODO_TYPE", "Birthday Call")%%% %%%FieldValue('<ContactFullName>')%%%

Schedule Tasks for Calls to Clients where the Birthday is in the Current Week or is Not Within Six Months

The workflow rule described in this section is triggered when a producer updates the Call Frequency field on the contact (client) record to 1-2 Times/Year. If the birthday of the client is within the current week or is more than six months from now, the workflow rule creates a review call task to call the contact six months from now.

Note: The expressions in this topic might appear across several lines due to length. All expressions in this topic must be entered in Expression Builder as one line and cannot contain any spaces. Also, the language-independent field names and the field-name syntax used in the expressions in this topic are the field names and syntax that were used in Expression Builder in releases earlier than Release 29 Service Pack 1. These expressions are still valid in Release 29 Service Pack 1 and later releases. However, starting with Release 29 Service Pack 1, Expression Builder uses language-independent field names and a field-name syntax that are different from the field names and the field-name syntax used in earlier releases. So, if you select the corresponding fields from the field list in Expression Builder when you create or update an expression in Release 29 Service Pack 1 or a later release, then the field names in the expression will be different from the field names shown in this topic, and the fields will appear in the expression editor with the following syntax: [{FieldName}]. It is recommended that you always select the fields for your expressions from the list of fields in Expression Builder, so that the field names and the field syntax are always correct. For more information about Expression Builder, see Oracle CRM On Demand Online Help.

Workflow Rule Details

This topic describes the details of the workflow rule.

Record Type

The record type is a Contact record.

Trigger Event

The trigger event is When New Record Saved.

Rule Condition

The Workflow Rule Condition field contains the workflow rule condition.

Enter the following expression in the Workflow Rule Condition field:

[<CallFrequency>]=LookupValue('PROF_CALL_CLASS','1-2 Times/Year') AND IIf([<DateofBirth>] IS NOT 
NULL, ((JulianDay(IIf(JulianDay(Mid([<DateofBirth>], 1, 6) + ToChar(Today(), 'YYYY')) < JulianDay
(Today()), Mid([<DateofBirth>], 1, 6) + ToChar(Today()+Duration("P1Y"),'YYYY'),Mid([<DateofBirth>],
1, 6) + ToChar(Today(), 'YYYY'))) > JulianDay(Today()+Duration("P6M"))) OR (JulianDay(IIf
(JulianDay(Mid([<DateofBirth>], 1, 6) + ToChar(Today(), 'YYYY')) < JulianDay(Today()), Mid(
[<DateofBirth>],1,6) + ToChar(Today()+Duration("P1Y"),'YYYY'),Mid([<DateofBirth>],1, 6) + 
ToChar(Today(), 'YYYY'))) <= JulianDay(Today()+7))),1)

Workflow Action Details

This topic describes the details of the workflow action.

Action Type

The action type is Create Task.

Task Type

The task type is a Review Call.

Due Date

The Due Date field contains a numeric value that is calculated by adding the value in this field to the date on which the task is created.

Enter the following expression in the Due Date field:

IIf((IfNull(Mid(1.0 * JulianDay(Today()+Duration("P6M"))/7, 8, 1), "0")>="7"),IIf((IfNull
(Mid(1.0 * JulianDay(Today()+Duration("P6M"))/7, 8, 1), "0")="7"),Today()+Duration("P6M")+2,Today()
+Duration("P6M")+1),Today()+Duration("P6M"))

Subject

The Subject field contains the subject line for the task. You can embed functions and field names in the text. Three percent signs (%%%) before and after an embedded function or field name indicate that it is to be converted to a string.

Caution: In the Subject field, three percent signs (%%%) are placed before and after the functions and field names. If you type a function or field name directly in the Subject field, you must type three percent signs before and after it. If you use Expression Builder to embed a function or field name, the percent signs are automatically added and must not be pasted into Expression Builder. When percent signs are pasted into Expression Builder, Expression Builder displays an internal error.

For more information about expressions, see Oracle CRM On Demand Online Help.

Enter the following expression in the Subject field:

%%%LookupValue("TODO_TYPE", "Review Call")%%%- %%%FieldValue('<ContactFullName>')%%%