bpm

Hi Michelle Plutto ,

You have a few potential solutions. Once I have answers to a few clarifying questions, I can provide you recommendations:

• What is the specialist field you are referring to? Is it a relate, relationship, dropdown, or text field?
• How many different entries are likely or possible in the specialist field? Is it typically only a handful of users or is it a more expansive list?
• Is the specialist field on the same record that triggers the process or is it on a related module? If it is on a related module, what relationship type does that module have to the triggering record (one-to-one, one-to-many, etc.)?

Thanks!

Chris

Hi there Chris,

It is a text field within leads (which I can modify if I should), this a pilot program for the lead module so hopefully eventually it will be quite a few with 25 possibilities (people) eventually. So, when the marketing status changes to "hot lead" it checks who was imported in the "specialist field" and then reassigns the lead and notifies the (new) assigned to person.

Hi Michelle Plutto ,

A text field isn't ideal because it presents the opportunity for non-standard inputs (e.g. typos, nicknames, etc.) that would not be able to be interpreted by BPM. We typically deploy a one-to-many relationship from the Users module to the target module to contain this type of data. Doing that ensures you have standardized data in the module and gives you a better foundation for building out automation strategies.

With regards to potential solutions, you have the following recommended options:

• Business Rule - As Bud Hartley mentioned, you can build out a business rule to handle the scenarios. The pro to this solution is that you could use your existing text field to handle the lead assignments. The cons to this solution are (1) it requires ongoing maintenance and (2) you may have unexpected outcomes due to aforementioned typos/non-standard entries with a text field. Business rules are not dynamic so any time you have a new user to add as a specialist, you need to update the business rule to account for that new user and properly assign the record.
• Upsert BPM Essentials - One of the features of our Upsert BPM Essentials plugin is to dynamically assign a user based on another user relationship value. The pro of this solution is that it is dynamic and would not require any ongoing maintenance. In your process definition, you would configure a single action element to set the assigned user to the dynamic value of the specialist field. The con of this solution is that you would not be able to use your existing text field. You would need to deploy a user relationship to use our custom action.

I hope this helps!

Chris

Hi Michelle Plutto ,

A text field isn't ideal because it presents the opportunity for non-standard inputs (e.g. typos, nicknames, etc.) that would not be able to be interpreted by BPM. We typically deploy a one-to-many relationship from the Users module to the target module to contain this type of data. Doing that ensures you have standardized data in the module and gives you a better foundation for building out automation strategies.

With regards to potential solutions, you have the following recommended options:

• Business Rule - As Bud Hartley mentioned, you can build out a business rule to handle the scenarios. The pro to this solution is that you could use your existing text field to handle the lead assignments. The cons to this solution are (1) it requires ongoing maintenance and (2) you may have unexpected outcomes due to aforementioned typos/non-standard entries with a text field. Business rules are not dynamic so any time you have a new user to add as a specialist, you need to update the business rule to account for that new user and properly assign the record.
• Upsert BPM Essentials - One of the features of our Upsert BPM Essentials plugin is to dynamically assign a user based on another user relationship value. The pro of this solution is that it is dynamic and would not require any ongoing maintenance. In your process definition, you would configure a single action element to set the assigned user to the dynamic value of the specialist field. The con of this solution is that you would not be able to use your existing text field. You would need to deploy a user relationship to use our custom action.

I hope this helps!

Chris