In what document of RUP should I put the Use case attributes (form fields)?
Suppose that there is a registration use case for some system. As a system analyst writing SRS, where could I write the specific attribute (form fields) of the registration use case? what is the name of this document?
Keep it simple and put that inside the same SRS.
Related
I have the following scenario that I need to put in place:
A user from SF must generate a contract with tables for a customer. As soon as the contract is generated, the user will handle the contract in a tablet to the customer, so he can sign it off in person.
To implement this I'm using DocuSign Gen to generate a template, because this particular template needs to have a table with multiple rows. So:
I declared all the Salesforce Fields I'm using on the contract .
I placed all the anchor texts on the MS Word file.
I declared all the DocuSign Fields (i.e. Signature, Name, Date Signed).
I also placed them all their anchor texts at the bottom of the MS Word file.
Finally, I selected a DocuSign Envelope (check the description below) template to streamline the signature delivery.
For the DocuSign Envelope, I simply created a template, but I didn't select any document, since that was going to be handle by the DocuSign Gen template. I defined the recipients (In Person Signer), and for the sending experience I selected the option Send Now: Skips all controls and sends the envelope immediately.
So, I was expecting that after clicking on the DocuSign Gen template button, the contract will be sent to the user so, he can handle the contract to the customer, to sign it directly.
Instead, after the contract is sent, and the user handled the control to the customer, they need to place AGAIN the DocuSign Fields (i.e. Signature, date, name) on the contract before signing it off.
How can I avoid that? I want neither the user nor the customer to place the fields again, since that's already defined on the template created on DocuSign Gen already.
It’s absolutely possible to set up an eSignature Envelope Template Configuration that works with anchor-tag/autoplacement, either with or without a static document pre-uploaded into the template. There are default anchor fields we offer out of the box that are listed in this support article. But it’s also possible to create your own custom merge fields with defined anchor text with the {r} wildcard placeholder.
The trick is to also ensure your recipients use the standard role naming conventions of “Signer 1”, “Signer 2", etc.
Example:
If you have \s1\ on the document, then that will get assigned to the recipient you’ve defined with the role name of “Signer 1”.
\s2\ for “Signer 2.” etc.
If you create a custom field with the defined anchor text of something like \ObjectName_FieldName_{r}\
Then on the document you place the text as \ObjectName_FieldName_1\
That field would be assigned to “Signer 1”
\ObjectName_FieldName_2\ would be assigned to “Signer 2" etc.
More information can be found here - https://support.docusign.com/s/document-item?language=en_US&bundleId=srl1586134368658&topicId=rvg1644270913133.html&_LANG=enus
From what I can tell, linking an Envelope Template to a Gen Template renders the Gen Template useless. I can't find any clear documentation about how they are supposed to be used together.
This is what I did:
Created a Gen Template with a Word document that has all of my anchors.
I wanted the Recipients to be auto-populated, so I also created an Envelope Template (without a document) and linked it to the Gen Template.
I expected that when I clicked the Gen Template button, it would use my tagged template, auto-choose the recipients, and send. However, as you stated, you have to replace all of the fields. I have no idea why.
I tried #inbar's suggestion of using autoplacement. I created a new document with these tags and uploaded it to the Envelope Template. This works as expected, but it seems to render the Gen Template useless.
At this point, I think the best route is to not use a Gen Template and just use an Envelope Template with autoplacement. I wish the documentation was more clear about how to use these templates together.
To create child record, I use e.force:createRecord but when I type the name of parent record into look-up field, it shows nothing even whole name or some letter.
I want to have the functionality as standard object like contact:
Do I need to config somewhere?
I believe Lightning shows only recently accessed records.
To have more flexibility you might need to create a completely custom component which would include custom lookup.
For my case I used custom components with custom lookup with similar approaches to this post or this one
I am using Joomla3 with tinymce editor. I have created one module and adding one params in textarea
I am adding iframe code
in text area
but it's not saving. If i am save normal text string then it's saving
Please help me
I believe you need to add a filter to your xml code.
such as:
filter="RAW" or, probably more appropriately, filter="HTML"
This will keep Joomla from cleaning your code. There are a number of filters available to XML fields when creating modules. You can examine the code here: https://github.com/joomla/joomla-cms/blob/master/libraries/joomla/filter/input.php#L167 to see the exact list.
What user group is the account you are using a member of? Super Users and Administrator group types should have no filtering set by default but it sounds like you might need to edit those settings.
From the main menu:
System > Global Configuration > Text Filters (tab)
You will see all the available user groups for you website. The group your user belongs to should have a Filter Type of No Filtering. Another important note is its better to add the user account to a group with the permissions then to arbitrarily adding it to a group type typically reserved for registrants, guests or low-level editing.
First sorry for my English, I'll try to be clear!
I would like to transfer a webform's data to a content type after the submission. Does a module exist to do this, or will I have to use a hook?
Case 1: one transfer new webform
you can use hook_form_submit() to directly get submitted data of all forms and choose your form with formId
Or use hook_form_alter() to add additional submit functions to the webfrom and then create a content using entity_create or node on form submit.
Case 2: use the Rules module for this purpose
If it's a migration of previous webforms then the solution is different.
I'm coding my first GAE web app in Python. I need to collect ~30 properties and instantiate a Client object (I'm using Model.db). I'd like to accomplish this on 4 separate sequential forms. If I use a separate page handler for each form, what is the best way to extract and reference the key or id on each form and put data into the same data entity? How do I avoid a global variable?
Not sure I follow... You may need to explain the issue a little more clearly.
First, do not use a global variable.
You can have 4 forms on the same template, all with the same handler. Give each a separate hidden attribute. Or, depending on your templating package, you should be able to access the form by ID.
In your handler:
entity = MyModel.get_by_key_name('my_key_name')
if request.method == 'POST':
if request.POST['hidden_field'] == 'firstform':
entity['prop_1'] = form.prop_1.data
...
if request.POST['hidden_field'] == 'secondform':
...
...
entity.put()
else:
return <template>
You will need to modify the syntax above to suit your templating pkg.