Tip #486: Don’t hard code currency in workflows

Bad currency workflow

If you have a workflow dealing with the entities that include money fields, avoid setting explicit currency. Instead, try to infer the currency from the related records. For mere mortals, it’s just a bad practice, for ISVs, it’s definitely a case of spießrutenlaufen. Why? Because if you activate your workflow and add it to a […]

Tip #420: If your child workflow needs more than one entity

Gaytime Multipack

CRM workflows always require an entity to run. But what if you’d like to create a child workflow but need more than one entity or additional parameters? For example, while identifying the business opportunities for a professional photographer, you may want to invoke a workflow called Book the ceremony that involves two people. Let’s assume […]

Tip #417: Cancel waiting instances in style

We have posted multiple times about waiting workflows, and one of the big challenges surrounding them is that when you update a workflow definition, there is no way to cancel the waiting instances of the workflow in bulk. Also, jobs may go into waiting state if there is a condition that prevents the step from […]

Tip #265: Administrator updates of read-only fields

If you have fields on your CRM form that are read only, it can make administration difficult. For example, if you have read only fields, you cannot bulk update the fields, and you can’t edit the field from the workflow designer. Sure you can customize the form, make the fields editable, and then bulk update the fields, […]

Tip #253: Keep your emails unique

Matching Senders Account

Say, you want to do some checks for inbound emails on Senders Account. It will work well until one of other email-enabled entities (typically systemuser) has a record with the same email address. Having multiple system entities (systemuser, contact, account) with the same email is a bad idea because, when system starts matching sender’s email […]