Welcome to the Sysero Knowledge Base

Please discuss with Sysero before use!  Important the use of this functionality should always be planned carefully, as has the ability to introduce costs all of it's own based on text message usage!

Please note currently we only support Amazon AWS SNS for sending sms text messages.  If you have another provider please contact us to discuss requirement.  Sysero do not provide the Amazon AWS SNS account.

SMS Text Messages can be used for two purposes in Sysero:

1. As an additional Two Factor method for authentication.
2. Ability to send text message via data action as notification.

In AWS SNS set the following settings

1. Default message type : Transactional
2. Account spend limit : Maximum USD you allow per month on text messages.
3. Default sender id : On message shows reciever source of message e.g. Sysero.

In AWS IAM settings setup the following

1. Go to Policies and Create policy.
2. In the JSON use syntax similar to the below, note the IP address is to stop other people using this service if Key and Secret are compromised.
   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "VisualEditor0",
               "Effect": "Allow",
               "Action": "sns:Publish",
               "Resource": "*",
               "Condition": {
                   "ForAnyValue:IpAddress": {
                       "aws:SourceIp": [
                           "{yourpublicip}/32"
                       ]
                   }
               }
           }
       ]
   }
3. Remember name of new policy
4. Go to Users and Add New User.
5. Set User name and select Access Key as option before clicking next.
6. Attach policy to that user.
7. Remember to copy the secret and access key at end of creation process.  These will be required in next phase.

In Sysero

1. Go to Admin > System > AWS SNS Message Settings.
2. Set the Key and Secret to those recorded when setting up IAM account.
3. Set ID to the SenderID you set in AWS SNS settings.
4. Set the AWS region the SNS was setup for.
5. Set limit to safe level for a month, recommend setting lower while testing.
6. If using two factor, set the two factor text.

Two Factor

Note you can only request a maximum of 3 two factor codes in a 3 minute period via this method for each user.

• Once the above has been setup, two factor is controlled by role User: Two Factor Authentication Can use phone.
• This also requires a user has a mobile phone number set in their User profile.

Data Action Send Text Message

Note for Data Actions you can only send 3 text message per minute for item you are working on.

Data action requires following input mappings:

1. Phone or User : If Phone used pass phone number, if User used pass UserID or Email and it will lookup Mobile phone from profile.
2. MessageText : Text of message you need to send.

Output mapping should be set to Status with No Output Mapping, this will give visual indication to success of text.

The below query string parameters are set when using worksiteupload.aspx in Admin > System > Integrations: iManage Work > URL Mapping:

• ApplicationID = ID of App/Data Room.
• CompanyID = ID of Site/Company.
• StorageType
  • SyseroStore (default) = Physical copy in Sysero.
  • IWL  = Legacy link to iManage.
  • URL = https link to Document in iManage.
  • Worksite (iManage Work) = Only ID stored in Sysero (prefer URL usually)
• Mode
  • Default = All selected documents to single Sysero profile.
  • MultiProfile = Single Sysero profile for each selected document.
• TextFieldx = You can use TextField1= to set default values on new profile.
• DocumentID = should be set to [documentid], this will be single or list of documents to upload.
• DocumentIDField = You can name the document field to store DocumentID in the Syser profile, this will allow for settings to only upload document once etc.
• UseExisting = If used in conjunction with the above, it will update existing profile not create new one.
• NoIndex = Do not index document content for links.
• ApplySecurity = Apply security rules, from iManage to new Profile.  Roles need to be mapped in Admin > Data Room > Worksite Settings > Worksite Role Mappings.
• The following additional pseudo code values can be set in URL:
  • [custom1]
  • [custom2]
  • [custom3]
  • [custom1_description]
  • [custom2_description]
  • [custom3_description]
  • [workspaceid]

Please note: inbuilt fields (author, doctype etc) fields are mapped using Admin > Data Room > iManage Work Settings > Inbound Field Mappings.

Coupled Data Rooms have the following Types:

• Parent to Children
• Child of Parent(s)
• Related

Below are a couple of scenarios to explain their usage:

1. If you have a Knowledge Library and you want to attach Drafting Documents to it, you would probably have two Data Rooms, Knowledge Library and Drafting Documents. 
   1. In the Knowledge Library Data Room you would create a Coupled Data Room Section.
   2. Set the Type to be Parent to Children.
   3. Set the Child Data Room to be Drafting Documents.
   4. Save the section and form.
   5. Although not necessary you could then show the Parents on the Drafting Documents Data Room by adding a Coupled Data Room Section.
   6. Set the Type to be Child of Parent(s).
   7. Set the Parent Data Room to be Knowledge Library.
   8. Make sure the correct section from Knowledge Library is selected.  If Knowledge Library was Coupled to other Data Rooms it would cause items to appear in wrong section if set incorrectly.
   9. Save the section and form.
2. For document automation where you require a data room to be linked as a child of another, you can do the following:
   
   1. Create a new data room for the child data
   2. In the main data room make a section that is a coupled data room section
   3. Set the type to be parent to children and select the child
   4. The fields menu in automated templates in the parent data room should now have the ability to add repeat tags for the coupled data room content on the parent section
3. If you have Knowledge Items that are often used together and they have equal relationship, so they should display if they are either children or parent items.
   1. Add section to Knowledge Library.
   2. Set the Type to be Related
   3. Select the related Data Room, in this case iteself but could be another.
   4. Select the related section, same reasons as in previous scenario.
   5. Save the section and form.

1. Logon to the Sysero instance that will be cloud facing or is accessible to those that need to sign documents, note if not same instance for both note down steps below where it is specific to seperate Sysero instnaces.
2. First you may want to create a new site dedicated to sigining.
3. Switch to the existing or newly created site you will be using for signing.
4. Create a App/Data Room and in Basic Settings set the Type to Signature Routing.
5. Go into Admin > Site > Signature Settings and set the following settings.
6. Enable Client as Signature Routing Host.
7. If this is a seperate Sysero instance copy the Access GUID for later in process.
8. Set the Email routing mode.
9. Create a Routing Email in Admin > Email Templates, remembering to add the [SignatureLink] place holder.
10. If you want to send a Final e-mail to all signatories once all signatures are on document, create another Email Template and select here.
11. Set the App/Data Room you created as the Signature routing Data Room.
12. See if any other settings are relevant to you.
13. Save the settings.

1. You now need to Login to the primary Sysero instance if hosting was on a different instance.
2. Go to site you will be configuring signing for.
3. If instance is the same check "Use Current Instance for Signature Server", otherwise follow these two steps:
   1. Host Sysero Instance URL, this will be the root URL for the seperate Signature Host instance of Sysero.
   2. Enter a signature routing site Access GUID, this is the GUID you noted down earlier.
4. If instance is the same as host you also need to select the site that is set for "Signature Host".

	The button on the right to expand comments will appear on Summary and Input forms if comments are enabled.
	If enabled in Sysero for Office the button will appear on the Sysero for Office ribbon.

1. To enable comments, set setting Admin > App/Data Room > Advanced Options > Feature Settings > Items: Allow users to leave review comments.
2. If you require the button in Sysero for Office on an open document, set setting Admin > App/Data Room > Office Settings > Enable Comments Button.
3. To allow users to set comments set Role Permission > App: Allow Review Comments.
4. To allow users to delete other peoples comments set Role Permission > App: Allow deletion of other user comments.

1. Sign by myself - Inserting a stored signature via a button click into any document.
2. Signature routing - Sending via e-mail for people to sign, often known as e-signing.

1. Go to Admin > Site > Office Settings > Enable Sign as myself buttons.
2. Any user using this will require Role Permission - User: Allow user to sign documents.
3. If you require the ability for users to delegate permission to sign documents on their behalf, enable delegation by going to Admin > Site > Signature Settings > Allow Signature delegation.

1. No Output : Display Value field from results returned.
2. No Output : Stored value field from results returned, hidden should be checked.