I am interested in making a Flow that connects to 2 fields, one field that gives a choice of the country (from the list of countries in the world) and a second field that is dependent on it that allows me to choose the city of the country that I chose. the api? And if so, how do you do it? In addition, what kind of flow is this implemented on?
It is required to create a Flow that allows the ACCOUNT object to be updated with the weather if a city in India is selected.
It is required to allow the user to select a country in Flow from a list of countries and a city from that selected country.
As soon as it is recognized that it is the country of India, the city must be updated in the custom field in the ACCOUNT object. If it is not India, there is no need to update the field.
When Contact's object records are updated, "Number of Updates" field will be updated as follows: The field should count the number of clicks on the "save" button in a specific contact record. Meaning, in every update, 1 will be added to the field's last value (every update: +1), For example: Number of Updates = 5 After saving the Contact's record, "Number of Updates" field value becomes 6 and so on.
1. Create a new field on Case: Name: Owners Manager Email Type: Email
2. Create a Flow (autolaunched) and a Process Builder: Flow Name: Case Owner Manager Email Flow Description: This flow is used to update Owners Manager Email field when Case is created or when the case owner is changed. Logic:
1. Check if the case owner is a User or a Queue.
2. If the owner is a Queue, or a User that has no manager, do nothing.
3. Else (the owner is a user with a manager), populate the field "Owners Manager Email" with the email of the owners Manager.
PB Name: Case PB Criteria: When Case is created or the case Owner is changed. Action: Launch Flow.
3. Create a Screen Flow & Action: Flow Name: Create Contact Flow Description: Screen flow to make it easier to create a contact.
Logic:
1. Show a screen with those contact fields: First name, Last name, Mobile and Email.
2. Check if a contact with the same mobile OR email already exist in the system.
3. If such contact already exists, show a screen "Contact already exist for Account xxxx" where xxxx is the Account name of that contact.
4. If the contact does not exist, create new contact under the current Account.
Create an Action on Account object that will launch the above flow OR put the flow on the Account Lightning page.
1. Create a new field on Case: Name: Owners Manager Email Type: Email
2. Create a Flow (autolaunched) and a Process Builder: Flow Name: Case Owner Manager Email Flow Description: This flow is used to update Owners Manager Email field when Case is created or when the case owner is changed. Logic:
1. Check if the case owner is a User or a Queue.
2. If the owner is a Queue, or a User that has no manager, do nothing.
3. Else (the owner is a user with a manager), populate the field "Owners Manager Email" with the email of the owners Manager.
PB Name: Case PB Criteria: When Case is created or the case Owner is changed. Action: Launch Flow.
3. Create a Screen Flow & Action: Flow Name: Create Contact Flow Description: Screen flow to make it easier to create a contact.
Logic:
1. Show a screen with those contact fields: First name, Last name, Mobile and Email.
2. Check if a contact with the same mobile OR email already exist in the system.
3. If such contact already exists, show a screen "Contact already exist for Account xxxx" where xxxx is the Account name of that contact.
4. If the contact does not exist, create new contact under the current Account.
1. Create a new field on Case: Name: Owners Manager Email Type: Email
2. Create a Flow (autolaunched) and a Process Builder: Flow Name: Case Owner Manager Email Flow Description: This flow is used to update Owners Manager Email field when Case is created or when the case owner is changed. Logic:
1. Check if the case owner is a User or a Queue.
2. If the owner is a Queue, or a User that has no manager, do nothing.
3. Else (the owner is a user with a manager), populate the field "Owners Manager Email" with the email of the owners Manager.
PB Name: Case PB Criteria: When Case is created or the case Owner is changed. Action: Launch Flow.
3. Create a Screen Flow & Action: Flow Name: Create Contact Flow Description: Screen flow to make it easier to create a contact.
Logic:
1. Show a screen with those contact fields: First name, Last name, Mobile and Email.
2. Check if a contact with the same mobile OR email already exist in the system.
3. If such contact already exists, show a screen "Contact already exist for Account xxxx" where xxxx is the Account name of that contact.
4. If the contact does not exist, create new contact under the current Account.
Create an Action on Account object that will launch the above flow OR put the flow on the Account Lightning page.
I am interested in making a Flow that connects to 2 fields, one field that gives a choice of the country (from the list of countries in the world) and a second field that is dependent on it that allows me to choose the city of the country that I chose. the api? And if so, how do you do it? In addition, what kind of flow is this implemented on?
It is required to create a Flow that allows the ACCOUNT object to be updated with the weather if a city in India is selected.
It is required to allow the user to select a country in Flow from a list of countries and a city from that selected country.
As soon as it is recognized that it is the country of India, the city must be updated in the custom field in the ACCOUNT object. If it is not India, there is no need to update the field.
When Contact's object records are updated, "Number of Updates" field will be updated as follows: The field should count the number of clicks on the "save" button in a specific contact record. Meaning, in every update, 1 will be added to the field's last value (every update: +1), For example: Number of Updates = 5 After saving the Contact's record, "Number of Updates" field value becomes 6 and so on.
1. Create a new field on Case: Name: Owners Manager Email Type: Email
2. Create a Flow (autolaunched) and a Process Builder: Flow Name: Case Owner Manager Email Flow Description: This flow is used to update Owners Manager Email field when Case is created or when the case owner is changed. Logic:
1. Check if the case owner is a User or a Queue.
2. If the owner is a Queue, or a User that has no manager, do nothing.
3. Else (the owner is a user with a manager), populate the field "Owners Manager Email" with the email of the owners Manager.
PB Name: Case PB Criteria: When Case is created or the case Owner is changed. Action: Launch Flow.
3. Create a Screen Flow & Action: Flow Name: Create Contact Flow Description: Screen flow to make it easier to create a contact.
Logic:
1. Show a screen with those contact fields: First name, Last name, Mobile and Email.
2. Check if a contact with the same mobile OR email already exist in the system.
3. If such contact already exists, show a screen "Contact already exist for Account xxxx" where xxxx is the Account name of that contact.
4. If the contact does not exist, create new contact under the current Account.
1. Create a new field on Case: Name: Owners Manager Email Type: Email
2. Create a Flow (autolaunched) and a Process Builder: Flow Name: Case Owner Manager Email Flow Description: This flow is used to update Owners Manager Email field when Case is created or when the case owner is changed. Logic:
1. Check if the case owner is a User or a Queue.
2. If the owner is a Queue, or a User that has no manager, do nothing.
3. Else (the owner is a user with a manager), populate the field "Owners Manager Email" with the email of the owners Manager.
PB Name: Case PB Criteria: When Case is created or the case Owner is changed. Action: Launch Flow.
3. Create a Screen Flow & Action: Flow Name: Create Contact Flow Description: Screen flow to make it easier to create a contact.
Logic:
1. Show a screen with those contact fields: First name, Last name, Mobile and Email.
2. Check if a contact with the same mobile OR email already exist in the system.
3. If such contact already exists, show a screen "Contact already exist for Account xxxx" where xxxx is the Account name of that contact.
4. If the contact does not exist, create new contact under the current Account.
Create an Action on Account object that will launch the above flow OR put the flow on the Account Lightning page.
