...
Questions | Details | Clarification | Status |
|---|---|---|---|
What kind of mechanism do we want to use for making the request from CITI to JIRA? | Do we want to use JSD customer portal forms or do we want to use JSD create customer request api or both? Does it depend on the request type? | There maybe some scenarios in parent child relationship where we may have to go ahead with request apis but for most of the scenarios we will be using the JSD form with pre-filled values from CITI | Resolved |
On what event do we have to send data from JSD to CITI app? | After creation of a request? | Unresolved | |
What are the different types of scenarios we will encounter while making a request from CITI app to JSD | parent/child relationship in orders | Unresolved | |
Whats a briefcase in CITI app? | In one of the mails it is mentioned that a briefcase in CITI app can be used to make an imaging order. Are there any other such features that we should know about? | Briefcase in CITI app is nothing but clubbing multiple objects from CITI into one request in JSD | Resolved |
What do you mean by dynamic functionalities of the form fields? | There are some places in mail chain where it mentions the term dynamic functionalities wrt JSD form fields. | Dynamic functionalities of the form means the ability of the JSD forms to validate the input or to pull the list of Users or list of issues and display them in the Issue picker or user picker respectively | Resolved |
Are the data points sent from CITI to JSD remain the same for different request types? | Object ID, Object title, Artist, Department, Object Type, Thumbnail path, Place ID/Place shortcut codes, Location/Place Name, Exhibition ID, Exhibition Title, Exhibition Opening Date, Exhibition Opening Date, Exhibition Closing Date, Exhibition Curator | They remain the same (only the actual values will differ). Also for one request type some proportion of these data points may be sent over to JSD and for other request type the remaining may be sent over for ex. for object photography the CITI app may send Object ID ,Object title, Artist, Department and Object Type, Thumbnail path but for conservation photography the CITI app may send Place ID/Place shortcut codes and Location/Place Name only | Resolved |
Transitions of requests through different workflows and process to follow for each workflow | Unresolved | ||
Communication NETX api | Unresolved |
Scenarios for handling multiple objects from CITI app (Applicable for New Object Photography, )
Briefcase Scenario(One JSD request with multiple objects)
Scenario | Each Object has same values for all fields in the JSD form | Each/Some Object/Objects has/have different field values in the JSD form |
Description | There should be a way for the CITI app to create multiple requests(tickets in JSD) using the JSD form for objects which have same values for all the fields in jsd form except the object ids which come from CITI app | There should be a way for the CITI app to create multiple requests(tickets in JSD) using the JSD form for objects which have different values for some or all of the fields on the JSD form. |
Conditions | A single fields should be there to capture different object ids in the form of some delimited values ex. Textbox(43243,54254,65433) | |
Ideas for implementation Let CITI app pass the data in the url along with delimited values for object ids and a flag to denote that this is a multi object request |
| |
Request parameters | type=case4 ids=343432,54353,32133214,54325,432421 | |
Comments | Use the creation event to create the tickets in the JSD using the info from JSD form and different Object Ids |
Parent/Child relationship(One JSD request with multiple children)
...