How to insert a currency field in DocuSign? - docusignapi

I am tring to create a DocuSign template and I need to be able to insert a field which shows a currency amount (for example $12.55 ). I need to show the dollar sign and possibly calculate the values based on other field values.
I am able to calculate values using a formula fields, but I don't see ho to mask the formula fields to show a dollar sign. The only workaround that I was able to come up with is to make a static text field with a dollar sign next to a formula field as show in the picture:
Is there a way to add a currency field (validation) in DocuSign?

No - your dollar sign workaround is the only real option, although you do want to make sure you make the $ field read only so the signer doesn't type anything into it.
It would be possible to use custom validation and regex to make a text field that accepts a dollar amount, but it wouldn't be usable with a Formula field. Formula fields only accept input from Number and Date validation fields.
There is an open Enhancement Request regarding this, but it has not been prioritized and is not currently on the roadmap for implementation. If you would like to express interest, contact your DocuSign Account Team and reference issue MAR-29946.

Related

Excel Check String is Valid with a Template

In Excel, I have this template for checking SMS format:
Your appointment is confirmed with [name] at [hh:mm] on [dd/mm/yy]. Please bring all your related documents.
The actual SMS will be the same except the tokens (delimited by brackets []) will replaced with actual values.
How can I check a list of SMSs if any SMS doesn't follow the previous template? I have multiple template with a list of SMS sent in one month.
If you have your input data in A2. You can use the following in B2:
=LET(texts, {"Your appointment is confirmed with "," at "," on ",
". Please bring all your related documents."},
SUMPRODUCT(--ISNUMBER(SEARCH(texts,A2)))=4)
LET is just to organize better the expression. It returns TRUE if all the input strings match, otherwise it returns FALSE. The rest is just to extend the formula down.
Here is the output:
Notes:
Excel doesn't have RegEx function, except via VBA. Check this link for this approach.
You can add additional checks for the token values introduced if you want, but based on your question, the above formula would be enough for your needs.

Changing decimal format of a calculated field in DocuSign

In one of my DocuSign templates, I have a fixed table and a summary row at the bottom. In the summary row, all above cells in the column are summaries with a formula field. The calculated amount, however, returns the result using a UK/US decimal format:
link to a picture of the problem
Is it possible to change the result from "1,235,678.00" to "1.235.678,00"?
It is not possible to change the decimal formal of a calculated field through settings as of the time of this writing. I contacted DocuSign support and I was referred to my account manager to have this fixed. I recommend to anyone walking in these shoes to either contact DocuSign support or contacting their account manager directly!

Saving SharePoint list item as draft without required fields

E.g. there is a list with gazillion required fields and I want the users to be able to fill out whatever they can and save as a draft until they have full info? Is there a simple solution for this? Tia!
Option 1: Multiple Content Types
One approach is to have two different Content Types on your list: one for draft items and one for submitted ones.
Content types on the same list can have different settings for the same columns. This means you can make the fields optional on the "draft" content type while making them required on the "submitted" content type.
The downside is that it may not be intuitive for end users if they're required to manually change the "Content Type" field in order to publish their draft.
Option 2: List Validation Settings
Another approach is to use List Validation settings instead of making fields required.
List validation lets you specify an Excel like formula (from which you can reference column values) which must evaluate to true in order for the validation to succeed. If it evaluates to false, a validation error message is displayed instead (you can specify the text of that message) and the item cannot be saved.
Simplified Scenario: One Field
Suppose you have a field called First Field that you don't necessarily need to be filled out right away, and you also have a choice field called Status Field that's used to indicate whether an item is a draft version or is submitted (displaying either "Draft" or "Submitted").
You can set up a list validation formula that requires First Field to be filled in whenever the Status Field is changed to "Submitted".
The formula would look like this:
=If([Status Field]="Submitted",NOT(ISBLANK([First Field])),TRUE)
In plain English, that formula is saying:
If Status Field is equal to Submitted...
...Then the form is valid only if First Field is not blank.
Otherwise, the form is valid.
More Complex Scenario: Multiple Fields
To make that work for multiple fields, you can join conditions together using the OR() and AND() functions, in the format of OR(condtion1,condition2)
So instead of ISBLANK([First Field]) to check whether a field is blank, you'd have something like OR(ISBLANK([First Field]),ISBLANK([SecondField])) to check whether either of two fields is blank. (Replacing First Field and Second Field with your field titles as appropriate.
The formula would now look like this:
=If([Status Field]="Submitted",NOT( OR(ISBLANK([First Field]),ISBLANK([Second Field]))),TRUE)
Note that you can nest multiple OR() conditions together arbitrarily, in the format of OR(condition1, OR(condition2, OR(condition3, condition4))) (and so on indefinitely).
Offloading Formula Complexity to Calculated Columns
If you run into limits with the formula length, you can offload some of your condition calculations into their own calculated columns, then just refer to those column values from your validation formula.
This can also help keep your formula from looking so complex.
For example, for every field that you want to be required, you can create a calculated column with a formula of =NOT(ISBLANK([Column Name])) and name it something like "{Column Name} Is Valid". Then you can refer to those columns in your validation formula:
=If([Status Field]="Submitted",AND([Field1 Is Valid],AND([Field2 Is Valid],[Field3 Is Valid])),TRUE)

How to Restrict Users to Sign as per date difference in docusign

I am working on one requirement where I have to show / hide Sign tag as per
the number of days calculation.
I tried to use two datafield for "Date" date type:
DateSigned = "11/05/2015"
DateReceived= "11/01/2015"
Added one more Datafield NumberofDays "number" type and added initial
value 14 days.
So , I want to calculate difference b/w to dates and if this difference is
greater than 14 days, I need to show Sign tag on documents else I need to
hide it.
I tried to use formula on template but it seems, not working
Formula is used = DateDiff([DateSigned], [DateReceived]) >
([NumberofDays])
I can always see Signature tag visible whether I update any value in
NumberofDays.
Is there any otherway like if we can open Recipiententer image description here/Signer view using Iframe and Iframe can be made read only.
your help is really appreciable.Attached image for reference.
Unfortunately the DocuSign conditional tab logic does not support greater than or less than operators. It only supports "equals specific value" or "not blank".
A crude workaround using the conditional logic tabs support: lets say i want a signature tab to appear if a delta is 1,2, or 3. I would create THREE unique signature tabs, each with specific conditional logic to appear if the delta/calculated value is 1, 2, or 3. If i needed to support 5 unique values, then that would result in 5 unique signature tabs. Granted, only ONE would actually be visible/appear based on the end calculation.

Currency summation in Lotus Notes

We have designed the LN forms with editable fields.User enters the amounts in the editable fields. We are converting the these amounts to currency using 'CCur'. The actual issue is user enters the amounts with decimal separator either as comma(,) or dot(.). When converting the amounts to currency it is not considering the decimal and thousands separator.
Example:
User enters amounts as below: Amount1 = 2090,Amount2 = 1500,90 and Amount3 = 800
In the current case the TOTAL AMOUNT is calculated as 152980.00 which should be 4390.90
How can I achieve this? Do we have user specific settings in LN which automatically takes care such things?
Regards,
Kishore
It sounds like your currency formats may not be set up correctly, and thus the locale of the client being used to enter the value 1500,90 is one that assumes the comma is a thousands separator, and the period is a decimal separator.
Here is one section of the documentation to check-out. You may need to confirm the field settings on the form to see if a custom currency format has been specified. Otherwise, see what the user preferences of the client says
For this question, I am not clear that why are you using comma as a decimal separator, I guess that it is not a formal way for storing the currency value. I can understand. this is your requirement. Just Take this as a suggestion. Okay We have the field property, First you change the field type as Number. And set the field control property, Number format is as currency and Change the User preference as Custom. There you can find two kind of settings enabled. Here you change the thousand separator into a different symbol. But I guess that you can not give multiple separator for decimal or thousands. Also If you give the same symbol for both things. It will be conflict.
My opinion- Based on your requirement, You do replace the comma with dot before applying the Ccur().
#Ramkumar: I don't agree. Set the field settings to Numeric and "User settings", not "custom". The users need to use the correct decimal point, if they are in a country where a period is used for decimal point, they use that, if they are in a country where they use comma as decimal point, they use that.
Kishore, you could add a field validation on the numeric field to make sure the value is numeric.
Use #IsNumber for this.

Resources