User Tools

Site Tools


msp_manage_customers

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
msp_manage_customers [2018/06/13 15:11]
willm
msp_manage_customers [2018/10/15 15:40] (current)
robyn.lin
Line 7: Line 7:
 The following update sets should be installed: The following update sets should be installed:
  
-1. Perspectium for ServiceNow update set+1. (Latest) ​Perspectium for ServiceNow update set <WRAP round info>be sure to  Finish Install, configure the Perspectium Properties, and Test Connection</​WRAP>​
  
-2. Perspectium ​MSP Base update set+2. Perspectium ​Common Endpoint ​update set
  
-3. Perspectium ​Deferred ​update set+3. Perspectium ​Common Incident update set 
 + 
 +4. Perspectium SIAM Mapping UI update set 
 + 
 +5. Perspectium MSP Gateway ​update set
  
  
 Once the update sets have been installed: Once the update sets have been installed:
  
-1) Go to Manage Customers (SP) tab under the Perspectium MSP app:+1) Navigate ​to the Perspectium MSP application menu and click Finish Install (this process may take several minutes to complete).
  
-{{:​manage_customers_sp_nav.png?200|}}+<WRAP info round>​Company should be previously added and configured under **Organization > Companies**The company domain should also be previously added and configured under **Domain Admin > Domains** </​WRAP>​
  
-2) The MSP Customers page has a list of all customers (5 customers per tab). To create a new Customer, click on the blue New button+{{:​msp_finish_install.png|}}
  
-{{:​msp_customers.png?400|}}+2) To create a new Customer, click on the Add Customer tab under the Perspectium MSP application menu (alternatively,​ you can also proceed to step 3 and click on the New button)You will be directed to the following page:
  
-You will be redirected to a page where the following information can be enteredCustomer Name textbox (mandatory),​ Customer Company lookup (not mandatory), and a checkbox indicating whether the Customer is Active or not+{{:msp_new_customer.png|}}
  
-{{:msp_create_new_cust.png?600|}}+Company (lookup field)populate with the company reference. Active checkbox: indicates whether the Company is Active or not (defaults to Active).
  
-3) Once you click Save, the sections for MSP Customer Endpoints and MSP Mappings will be generated below (these sections will be blank).+3) To see a list of all customersgo to the Manage Customers tab under the Perspectium ​MSP application menu
  
-{{:save_new_customer_detail.png?400|}}+{{:msp_manage_customers.png|}} 
 + 
 +Drill into the newly created customer; on this customer detail page, click New to create a new endpoint. This will open the following form (refer to section below).
  
  
 ==== Creating a New Customer Endpoint (ServiceNow) ==== ==== Creating a New Customer Endpoint (ServiceNow) ====
  
-Click on the blue New button on MSP Customer Endpoints. This will open the following form: +{{:msp_new_cust_endpoint.png|}}
-{{:new_msp_cust_endpt.png?400|}}+
  
-**Customer**: will be pre-populated with the current ​customer ​name.+**Company**: will be pre-populated with the current ​company ​name.
  
-**Endpoint Type**: a dropdown with the choices of ServiceNow, HP Service Manager, ​and Remedy. If ServiceNow is selected, the fields User, Password, and Requires Repeater Agent will be greyed out as ServiceNow does not use these fields. ​+**(EndpointType**: a dropdown with the choices of ServiceNow and Remedy. If ServiceNow is selected, the fields User, Password, and Requires Repeater Agent will not appear ​as ServiceNow does not use these fields. ​
  
-**ITSM Module**: a dropdown with one choice of Incident Management; currently this will be the only supported module in MSP Version 1.+**ITSM Module**: a dropdown with one choice of Incident Management
 +<WRAP round info> 
 +Currently Incident Management ​will be the only supported module in MSP Version 1. 
 +</​WRAP>​
  
-**Active**: a checkbox indicating if the endpoint is active or not.+**Integration User**: this field is automatically populated with generated user based on company name. You can also use the dropdown menu to change the integration user.
  
-**Endpoint URL**: the customer/​target endpoint URL (if an Endpoint Alias is not specifiedthis field will be used as the Source/​Target System display name when generating ​the MSP Mappings table).+*In order to trigger replication of incidents, the domain of the incident (based on caller'​s companyand the customer endpoint domain must match.
  
-**Replication Group**: represents ​the assignment group for incidents+**Active**: a checkbox indicating if the endpoint is active or not.
  
-**Endpoint ​Alias**: this field is optional; if you choose to give this endpoint ​an alias it (instead of the Endpoint ​URL) will be used as the Source/​Target System display name when generating the MSP Mappings table.+**Endpoint ​URL/​Instance**: the customer/​target ​endpoint ​URL or instance name (for ServiceNow endpoints). If an Endpoint ​Alias is not specified (below), this field will be used as the Source/​Target System display name when generating the MSP Mappings table.
  
-Once you click Save (or Save and Exit), the MSP Endpoint Table with the newly added endpoint will be generated. In addition, ​the Table Map, Transform Map, Dynamic Share, and Shared Queue will automatically be generated for this newly created endpoint configuration. If you click on the "Edit Dynamic Share" link (on the far right), it will direct you to the generated dynamic share+**Endpoint Alias**: this field is optional; if you choose to give this endpoint ​an alias it  ​will be used as the Source/​Target System display name when generating ​the MSP Mappings table (instead of the Endpoint URL).
  
-{{:​msp_cust_endpt_table.png?600|}}+Once you click Save (or Save and Exit), the MSP Endpoint Table with the newly added endpoint will be generated. In addition, the Table Map, Transform Map, Dynamic Share, and Shared Queue will automatically be generated for this newly created endpoint configuration. If you click on the "Edit Dynamic Share" link, it will direct you to the generated dynamic share. If you click on the "View Import Set Table" link, it will direct you to a list view of the dedicated import set table for this customer endpoint
  
 In addition, the MSP Mappings table will automatically be generated below the endpoint table (see screenshot below). ​ In addition, the MSP Mappings table will automatically be generated below the endpoint table (see screenshot below). ​
Line 61: Line 69:
  
  
-==MSP Mappings table==+====MSP Mappings table====
  
-Describes the bidirectional flow of messages from the Source to Target system. The rows on the Mappings table cannot be edited.+Describes the bidirectional flow of messages from the Source to Target system. ​*The rows on the Mappings table cannot be edited.
  
-**Source system**: indicates where the message originated from. As mentioned before, if an Endpoint ​Alias was provided in the endpoint configuration it will be used as the Source ​System ​value.+**Source system**: indicates where the message originated from. As mentioned before, if an Alias was provided in the endpoint configuration it will be used as the Source ​system ​value, otherwise it will default to the Endpoint URL.
  
-**Message**: type of the source message.+**Source Format**: type of the source message.
  
 **Maps to**: the "maps to" link will direct you to either the (previously generated) table map or transform map, depending on the direction of the message. ​ **Maps to**: the "maps to" link will direct you to either the (previously generated) table map or transform map, depending on the direction of the message. ​
  
-If there is no "maps to" and only an arrow, this indicates there is no transformation occurring.+**Target Format**: type of the target message.
  
-**Message**: type of the target ​message.+**Target System**: indicates ​the message's target destination. If an Alias was specified in the endpoint configuration it will be used as the Target system value, otherwise it will default to the Endpoint URL.
  
-**Target System**: indicates the message'​s target destination. As mentioned before, if an Endpoint Alias was provided ​in the endpoint configuration it will be used as the Target System ​value.+====MSP Share Conditions==== 
 +The conditions specified ​in this related list define ​the conditions that must be met for replication to occur and the action suffix produced in the name field of the outbound message. ​  The conditions are executed in sequence from lowest to highest order value. 
 + 
 +{{:​ShareConditions.png|}}
  
 ==== Creating a New Customer Endpoint (Remedy) ==== ==== Creating a New Customer Endpoint (Remedy) ====
  
-(Not completed) +[[http://​wiki.perspectium.com/​doku.php?​id=msp_remedy_endpoint|Remedy ​Customer Endpoint]]
- +
-==== Creating a New Customer Endpoint ​(HP Service Manager) ==== +
- +
-(Not completed)+
  
-=== Viewing ​Customer === +==== Viewing ​an Existing ​Customer ​==== 
-To drill into and view endpoint and mapping details for an existing customer from the MSP Customers home page, click on the row with the customer'​s name (ex: Acme).+To drill into and view endpoint and mapping details for an existing customer from the MSP Customers home page, click on the row with the customer'​s name. This will display all the endpoints for this customer.
  
-{{:​msp_existing_cust.png?600|}}+{{:​msp_existing_cust.png|}}
  
 +<WRAP round info>
 ***Note**: if you click the Active checkbox on the top of the page (as seen in the screenshot above), the Dynamic Share(s) and Transform Map(s) for all the customer'​s corresponding endpoints will be activated/​deactivated accordingly to prevent data from flowing in/​out. ​ ***Note**: if you click the Active checkbox on the top of the page (as seen in the screenshot above), the Dynamic Share(s) and Transform Map(s) for all the customer'​s corresponding endpoints will be activated/​deactivated accordingly to prevent data from flowing in/​out. ​
 +</​WRAP>​
  
-To drill into an endpoint configuration record, click on a row in the MSP Customer Endpoints table.+To drill into an endpoint configuration record, click on a row in the MSP Customer Endpoints table. This will display the endpoint record as well as its corresponding mappings.
  
-{{:​msp_existing_cust_endpt.png?600|}}+{{:​msp_existing_cust_endpt.png|}}
  
 +<WRAP round info>
 ***Note**: If you click the Active checkbox to activate or deactivate an endpoint the Dynamic Share and Transform Map for that specific endpoint will be activated/​deactivated accordingly. ​ ***Note**: If you click the Active checkbox to activate or deactivate an endpoint the Dynamic Share and Transform Map for that specific endpoint will be activated/​deactivated accordingly. ​
 +</​WRAP>​
  
-=== Deleting a Customer/​Customer Endpoint ​=== +==== Export to UpdateSet ==== 
-1) **Deleting a customer**: once you click/confirm Delete ​on the Customer Detail page, the customer and all its associated Endpoints and Mappings ​will be deletedalong with the associated ​Table Map, Transform Map, Dynamic Share, and Shared Queue artifacts+If you click on this button, the current ​customer, endpoint record, ​and all the previously generated artifacts (Mappings, ​Import Set Table, Dynamic Share, ​Table Map, Transform Map, and Inbound Table Map) will be pushed to the current update set. The Share Conditions will also be pushed to the current update set.
  
-{{:​msp_customer_delete.png?​600|}}+==== Deleting a Customer Endpoint ==== 
  
-2) **Deleting a customer endpoint**: once you click/​confirm ​Delete on the MSP Customer Endpoint record, that specific endpoint and its associated Mappings will be deleted, along with the associated Table Map, Transform Map, Dynamic Share, and Shared Queue artifacts. ​+**Deleting a customer endpoint**: once you click Delete on the MSP Customer Endpoint record, that specific endpoint and its associated Mappings will be deleted, along with the associated Table Map(s), Transform Map, Dynamic Share, and Shared Queue artifacts. ​
  
-{{:msp_endpt_delete.png?600|}}+<WRAP round info> 
 +***Note**The Delete action has been hidden for Customers Best practice is to not delete but rather deactivate customers. 
 +</​WRAP>​
  
  
msp_manage_customers.1528927901.txt.gz · Last modified: 2018/06/13 15:11 by willm