+4I have not done a complete audit, but the name property is missing from the listTabs object.
If we need a duplicate listTab for a conditional rule, we need to have a consistent name while the tabLabel must be unique.
Refer to the following documentation, and select create recipient tabs and you will see the issue:
+4Scott, thanks again for sharing valuable feedback and engaging with us.
We have discussed this here with the engineering team and we do have some questions about this.
First question - is there anything you are trying to do using our APIs that you’re unable to perform right now? We’re trying to take this first on the practical level - anything we can do to help you and your team with what you’re building.
second question, is this just about having a name property, what would the name property do?
Did you mean that tabLabel should have been called name? or having another property called name? and if so - what would this property do?
Also, as you can imagine, we cannot just rename tabLabel to name as this will break many existing integrations.
+4OK this is a blast from several months back, but I believe I recall this use case. It was for a USDA program where we created a data collection template, and we were trying to pre-populate the template with what we knew already about a farmer, including their arable fields and the farming practices performed on those arable fields. This included lists of the types of crops planted, fertilizer applied, and so forth, related to improving soil health. The current administration pulled funding for these programs, so the USDA was forced to hold back on financial commitments to farmers, and we had to back off on our grant. The template may be in our demo account, but we dropped this work so it is not an urgent.
But I do think the problem is relevant. We use JsonPatch libraries to pre-populate ‘value’ properties in numerous tab JSON before applying that to a template. We wanted another property called name so we could use the classic name/ value pair approach. For example, if this was fertilizer data, the ‘tabLabel’ would be ‘fertilizer’, the ‘name’ would be a type of fertilizer, e.g., ‘organic’ or ‘commercial’ and the ‘value’ could be a static permissible list of values such as a range of the amount (1-500 lb/acre, 501-1000 lb/acre, etc.). There were a lot of other use cases and the name property would allow our JsonPatch op, path, value code to be consistent, specifically in the path to match to the correct array entry to replace the value.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Back to Docusign.com
