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/07/27 17:56] (current)
robyn.lin
Line 9: Line 9:
 1. Perspectium for ServiceNow update set 1. Perspectium for ServiceNow update set
  
-2. Perspectium ​MSP Base update set+2. Perspectium ​SIAM Base update set
  
-3. Perspectium ​Deferred ​update set+3. Perspectium ​Common Endpoint update set 
 + 
 +4. Perspectium Common Incident update set 
 + 
 +5. Perspectium MSP Base 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) Go to Manage Customers tab under the Perspectium MSP app:
  
-{{:manage_customers_sp_nav.png?200|}}+{{:manage_cust_menu.png?200|}}
  
-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_customers.png?400|}}+2) The MSP Customers page has a list of all customers (10 customers per tab). To create a new Customer, click on the blue New button
  
-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_customers.png?600|}}
  
-{{:​msp_create_new_cust.png?​600|}}+You will be redirected to a page where the following information can be entered: Customer Name textbox (mandatory),​ Customer Company lookup with a dropdown list of vendors for a customer (not mandatory), and a checkbox indicating whether the Customer is Active or not.  
 + 
 +{{:​msp_create_new_cust.png?​|}}
  
 3) Once you click Save, the sections for MSP Customer Endpoints and MSP Mappings will be generated below (these sections will be blank). 3) Once you click Save, the sections for MSP Customer Endpoints and MSP Mappings will be generated below (these sections will be blank).
  
-{{:​save_new_customer_detail.png?​400|}}+{{:​save_new_customer_detail.png?​|}}
  
  
 ==== 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: +Click on the blue New button ​in the MSP Customer Endpoints ​section. This will open the following form: 
-{{:​new_msp_cust_endpt.png?​400|}}+{{:​new_msp_cust_endpt.png?​600|}} 
 + 
 +The Advanced section can be expanded/​collapsed.
  
 **Customer**:​ will be pre-populated with the current customer name. **Customer**:​ will be pre-populated with the current customer name.
Line 42: Line 49:
 **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. ​ **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. ​
  
-**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. **Active**: a checkbox indicating if the endpoint is active or not.
Line 48: Line 58:
 **Endpoint URL**: the customer/​target endpoint URL (if an Endpoint Alias is not specified, this field will be used as the Source/​Target System display name when generating the MSP Mappings table). **Endpoint URL**: the customer/​target endpoint URL (if an Endpoint Alias is not specified, this field will be used as the Source/​Target System display name when generating the MSP Mappings table).
  
-**Replication Group**: represents the assignment group for incidents. ​+**Replication Group**: represents the assignment group for triggering replication of incidents. ​
  
-**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 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).
  
-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. ​+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. The Scheduled Job column will be blank for ServiceNow endpoints as it only applies to Remedy endpoints.
  
-{{:​msp_cust_endpt_table.png?​600|}}+{{:​msp_cust_endpt_table.png?​|}}
  
 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 63: Line 73:
 ==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 Endpoint Alias was provided in the endpoint configuration it will be used as the Source System value.
Line 71: Line 81:
 **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.+If there is no "maps to" and only an arrow symbol, this indicates there is no transformation occurring.
  
 **Message**:​ type of the target message. **Message**:​ type of the target message.
  
-**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.+**Target System**: indicates the message'​s target destination. ​If an Endpoint Alias was specified ​in the endpoint configuration it will be used as the Target System value, otherwise it will default to the Endpoint URL.
  
 ==== 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) ==== ==== Creating a New Customer Endpoint (HP Service Manager) ====
Line 85: Line 95:
 (Not completed) (Not completed)
  
-=== Viewing a Customer === +==== Viewing a 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 (ex: GTX 1080).
  
-{{:​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.
  
-{{:​msp_existing_cust_endpt.png?​600|}}+{{:​msp_existing_cust_endpt.png?​800|}} 
 + 
 +There is an Audit History link at the bottom which enables you to view the history of changes to this specific endpoint record.
  
 +<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 === +==== Deleting a Customer/​Customer Endpoint ​==== 
-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 deleted, along with the associated Table Map, Transform Map, Dynamic Share, and Shared Queue artifacts. ​+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 deleted, along with the associated Table Map(s), Transform Map, Dynamic Share, and Shared Queue artifacts. ​
  
-{{:​msp_customer_delete.png?​600|}}+{{:​msp_customer_delete.png?​|}}
  
-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. ​+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(s), Transform Map, Dynamic Share, and Shared Queue artifacts. ​
  
-{{:​msp_endpt_delete.png?​600|}}+{{:​msp_endpt_delete.png?​|}}
  
  
msp_manage_customers.1528927901.txt.gz · Last modified: 2018/06/13 15:11 by willm