I'm working on requirement in Salesforce Marketing Cloud, where I need to include an expiration date field in payload sent to MuleSoft for each recipient in my request to send SMS so that when the rules engine in MuleSoft tries to re-send the message, it knows how long the request is valid based on the Expiration field.
These are my acceptance criteria :
1.Payload sent to MuleSoft includes a date/time for expiration for each recipient
2.The date/time for expiration is optional
3.Any SMS that has an expiration date/time in the pass is not re-sent by MuleSoft.
Could you please advise , how can we achieve this in SFMC?
Note: As part of previous deployment we have developed a custom activity having three fields on its UI, like SMSID, SMSText, and a dropdown field Transaction Type, which we use in jounrey builder.
As part this new requirement we need to have this expiration field added on to this custom activity.
Related
We use Docusign within our Salesforce instance, we have a couple of different options when selecting Recipient ID verification, SMS, Knowledge based, etc..My question is where would I tell Docusign to default on a specific authentication process.
For example. Say I click a Docusign Status button on the opportunity, it automatically brings in the recipient from set as the primary contact of the opportunity, and uses the CEM ,subject etc... from Docusign. Where can I if anyplace, dictate to have an ID verification method on?
Called Docusign Support, Apparently the only parameters you can pass into the button is for the SMS Verification and the Code Verification. The KBA authentication is not supported yet.
I would like to send email notification to Clients 1day before it's 30Days Trial Subscription ends based on the CreatedDate. Any suggestions would be appreciated.
Thank you!
Create an Workflow Rule and setup an Email Alert. You can create the Workflow Rule based off of a date and have it send an email template.
Create a Time-Dependent Workflow Action on a workflow rule when the record is created. The Time-Dependent Workflow Actions should be based on the Subscription End Date and should be 31 Days Before Subscription End Date. That way you don't have to worry about it. It'll just happen.
You can always look up pending actions in the Time-Based Workflow page in the setup area
In your question you mentioned the Created Date, if the Subscription end date is a fixed date from the created date that just factor that into the days before, but I think a separate end date gives more flexibility for scenarios such as extending a subscription.
Concatenate inbound email messages into a single google document each week and share that document via email. Inbound messages would be filtered into to a specific gmail label as a means of identifying them. A follow-on enhancement would be to lookup the name of the person submitting the request based on the inbound email address in a google contact and add that to the messages concatenated into the google doc.
I have a scenario and looking for a good database design. My application provide 3 different roles. Admin, Customer, and Narrator.
Customer choose a Narrator and request a service. His request process by Admin to check whether it is valid or not. If it is not valid, Admin will send it back to the Customer with a message. Otherwise, Admin will send the request for the chosen Narrator. The Narrator perform the request and send it back to the Admin. Admin will check it again against some circumstances. If validation fail, Admin send the request back to the Narrator with a message. Otherwise, Admin will mark that request as finished and send it to the Customer.
Here is my basic tables:
User
username
password
email
Narrator
image
rank
user_id (FK)
Customer
phone_number
address
user_id (FK)
Request
customer_id (FK)
narrator_id (FK)
...
Actually my problem is how I should design my tables in order to support such a transaction.
I appreciate your suggestions.
Your text explaining what kind of service you want to deliver is a good lead about what type of models you need. You write about 'admins' and 'messages' but those models are omitted. I also think that 'request' is a property of a Service.
Maybe go for more general terms? Client, Supplier, Message, Service, Manager, Product. The Service needs a state field: new, assigned, needs more X...
Then your story goes as follows:
A Client chooses a Supplier and sends a Message to request a Service. A Service request is created with the status 'new'. The request will be reviewed by a Manager: He sets the state of the Service to approved and with that one click also send notification Messages to both Client and Supplier. The Supplier will preform the Service and on completion change the state... et cetera.
I wonder where Invoice comes in and maybe you need to deliver a Product in the end.
This query is related to Google Apps. Is there a way we can get a trigger or a callback or force the user to visit a page from my app when user deletes my app from his domain?
I want to perform some operations when a user deletes the app from his domain.
Please help.
No. Mappings are completely independent of the app - they just 'point' at it. You can't get notifications when a user adds or deletes them.
The license notifications API allows you to retrieve a list of license-related events that have occurred for customers of your application. These events may be of four types:
provisions — A new license of the application has been provisioned.
expiries — A license of the application has expired.
deletions — An application has been deleted from a domain.
reassignments — An administrator has assigned or revoked a seat license for the application on the provided domain.
The license notification API allows several optional parameters:
timestamp — The time, measured in milliseconds since the UNIX epoch, to begin querying for notifications. The API will return results that occurred approximately after this time, but occasionally may return results that occurred prior to the timestamp. If you must have a list of notifications that only contains results after the timestamp, it is recommended that you apply a second filter in your code. The timestamp may not be used simultaneously with a start-token.
start-token — A continuation token, returned from a previous query, that may be used to continue retrieving notifications after the previous result set stopped. The start-token may not be used simultaneously with a timestamp.
max-results — The maximum number of notifications to return.
For a complete description of all response fields and possible values for those fields, see the reference.
For more : http://code.google.com/googleapps/marketplace/v2/developers_guide.html#license_notifications