Timeline for Send mail when contract is less than X days from expiry
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 12, 2019 at 17:21 | comment | added | Tanaka Saito | That is true, I omitted that detail, will edit the original question to have that info. Currently I'm thinking if I create a dummy field and update that through dataloader.io I should get the same result, which would allow me to work with a single workflow rule. Will update on the results tomorrow when the rule should have run. | |
| Jan 12, 2019 at 14:21 | comment | added | David Reed | One route could be a second Workflow Rule firing on edit, whose entry criteria include a Custom Permission that you assign to a data load user. You could then execute a no-change update (I call it a "ping") to your existing contracts as the data load user to get their emails scheduled, without worrying about the workflow interacting with new data. | |
| Jan 12, 2019 at 13:57 | comment | added | David Reed | It would be helpful if your question could clarify that you are working with existing data. You cannot make existing records have a time trigger scheduled without editing them and having the workflow rule fire. | |
| Jan 12, 2019 at 4:04 | comment | added | Tanaka Saito | The problem I have is also related to existing contracts. We have hundreds if not thousands of contracts with different customers that are currently active, and we edit existing ones when they renew their contracts. Having a rule only run on create will only be applied to new customers and will not work for existing records. I have made it work for new contracts with just process builder and/or workflow rules, I'm here trying to find a way to make sure that existing contracts that most likely will not be edited are also included. | |
| Jan 11, 2019 at 19:26 | history | answered | David Reed | CC BY-SA 4.0 |