Difference between revisions of "Receiving from Settings"

From SmartWiki
Jump to: navigation, search
 
m (Receiving from Settings)
Line 5: Line 5:
 
[[Image:402uta.png]]
 
[[Image:402uta.png]]
 
   
 
   
The following settings are used to configure the receiving from instance:
+
The following settings are used to configure the receiving from [[Instance|instance]]:
  
* '''Alias''' - The alias of sending SmartSimple instance.
+
* '''Alias''' - The [[Alias|alias]] of sending [[SmartSimple]] [[Instance|instance]].
* '''Id''' - Arbitrary two digit number unique to sending instance.
+
* '''Id''' - Arbitrary two digit number unique to sending [[Instance|instance]].
* '''Description''' - The full company name of sending instance for identification.
+
* '''Description''' - The full company name of sending [[Instance|instance]] for identification.
* '''Unpack Workflow''' - A workflow to be executed when the package is unpacked.
+
* '''Unpack Workflow''' - A [[Workflow|workflow]] to be executed when the package is unpacked.
  
 
==Key Settings==
 
==Key Settings==

Revision as of 15:52, 31 October 2007

Receiving from Settings

This section defines the alias, description and workflow to be associated with packages received from the sending instance.

402uta.png

The following settings are used to configure the receiving from instance:

  • Alias - The alias of sending SmartSimple instance.
  • Id - Arbitrary two digit number unique to sending instance.
  • Description - The full company name of sending instance for identification.
  • Unpack Workflow - A workflow to be executed when the package is unpacked.

Key Settings

This section is used to store the key generating in the sending instance and the source URL of the sending instance.

403.png

The values are as follows:

Acceptance Key - Combination of Id and Alias of the sending instance. Decryption Key - Key code generated by system of the sending instance. Source URL - The URL of the sending instance.

Unpack Rules

Unpack rules are used to define if new templates (Level 1) and types (Level 2 and Level 3) should be rejected in an incoming package.

404uta.png

Company and People Import Settings

This section defines how attached companies and contacts should be handled when received in a package.

405uta.png

Exporting Companies and Contacts

You can also export the companies and contacts associated with the UTA item when exporting the item. Using this technique, these companies and contacts will be recreated within the receiving instance if they don’t already exist.

397uta.png 401uta.png

Email Settings

These settings define an email alert when package arrives from sender. This email will be automatically generated by the system.

406uta.png

  • Acknowledge Users - Email addresses of recipients or groups. Use the Lookup button to select users.
  • From Address - Sending email address if appropriate. If this address is not entered, the address smartsimplemailer@smartsimple.com.
  • Subject - Message subject for email alert.
  • Body - Email message to recipient.

Protecting Fields

This section is used to define the Level 1, Level 2 and Level 3 fields to be protected.

407uta.png

  • By default, NO FIELDS are protected so all fields will be updated from the incoming information.
  • By default, the Level 1 fields are displayed. If you have enabled Level 2 and Level 3 entities, then tabs will be displayed so you can access and enable these fields.
  • If you enable Company & Contact Settings, then additional tabs will be displayed so you can protect fields in these entities also.

Setting the Receiving Settings

1. Set up the details of the sending instance in the Receiving From Settings.

408uta.png

2. Set up the Acceptance Key, Decryption Key and Source URL based on the sending instance.

409uta.png

You will need to copy the decryption key from the sending instance into the receiving instance.

3. Leave the three Unpack Rules unchecked.

410uta.jpg

4. Set the Company & People Import Settings to import all companies and contacts.

411uta.png

5. Click any Save button.

As you are not going to protect any fields in this example, the set up is complete.