Documentation Suggestion

Can we have documentation for each of the due date methods available in the product with examples and how does the Add, Subtract and other settings within the flavour when calculating the due date.

We need a document that explains the reasons for automatic disablement of email connectors.

Need Documentation on the Approval sheet which includes guidelines on, what is mandatory on the Approver Sheet, what cannot be deleted (Rows, Approval 1, 2 etc), How to set up the Approver Sheet, and what's Output required in the Approver Worksheet. Also Need to explain how to test the values when the parameters are of Normal Data Fields e.g. Multi Level List, Currency Field, Date Field etc.. It would be good to have examples for all the Data Field types. Also, need to highlight that Table Fields cannot be used in Approvals. For Approvals to work the email addresses should exist in the system.

There should be some content to explain users how daylight savings are taken care of in Enate, and what changes they need to do on Builder, if any.

we are looking for something which can explain the following with screenshots: • Basic AD setup, which we already have on our docs • Setting up creds for Office 365 Integration – we have two options: o Connect using certificate. o Connect using client secret. – if we can show how to create both of these in AD • The exact list of permissions to be given to the mailbox • Creating security groups to limit the permissions of a mailbox • What exactly happens in the background when we “Test Connection” for incoming & outgoing o Which component of mailbox Enate connects with to test All of this is to explain how to setup AD rather than Enate.

Can we please have documentation on how to override the default SMTP configuration to send outbound emails i.e. use a specific email address to send emails instead of default SMTP.

Can we have a document on how to use Web APIs? Basically looking for a flow of web apis to be called. Example: To update an action, user needs to first authenticate and then get the action guid and then update action. Having a document with this flow and parameter values helps

Hi Can we get more information on the syntax of how to specify subject lines in routing rules. Can we get the below issue I experienced included in documentation as well as any other tips? Examples: is it possible to specify that the keywords can only be at the start/end of the subject line? Specify keywords are case sensitive etc ____________ Hi We are looking to put in a routing rule so that emails that have the following in their subject will route to specific location: FW: 01 01 4 01 9 01 - I have set this up in the routing rule as: FW: 01;01 4;01 9;01 -; I have tested this and created a ticket in live mode for each subject and they are correctly routing. However I also then sent in tickets with subjects "01 3", "013827439" and these are routing to the same place as above rule instead of going to the other fall off routing rule that I have. Can you assist please - is the syntax "FW: 01;01 4;01 9;01 -;" correct? Hi Elaine, The syntax used in this particular routing rule ends with the semi-colon(;) hence it considers a blank entity after it, and since it has a higher priority than the second routing rule... therefore the tickets are getting created under that same category irrespective of any subject line. Correct Syntax: "FW: 01;01 4;01 9;01 -" Hence, the semi-colon needs to be removed from the end to make it function as per the required behavior. Regards, Rajnandinee Gokhe

Similar to validation examples for custom card, can we have example code for show/hide fields based on selected value from list please.

We can configure timezone at contract level, user/bot profile, calendar. Can we have explainer documentation significance of time zone at each level. if we can also have explainer on how time zone and no of hours per day is considered for due date calculation it would be very helpful.