The connection between our DAS and the base application is established by selecting an element (button, text fields, panel, link) of the base application using Newired Editor. This connection means that we record the information that a given step is connected to a place on the screen. We store information about the structure of the page on the base application, not about the end users nor the company’s own data.
For example: there is a ‘dropdown field in the UI of the base application to select the country of the contact. If there is a step in Newired Journey connected to that element, we remember that the element is a ‘dropdown’ menu, with the text ‘country’, but we do not store any of the data selected or provided on the base application, i.e., the actual country selected by the end user. In other words, the connection of the base application and our solution is established on the “container” level (page structure), not on the content level (input provided).
This connection between guidance and target app is setup only once by the DAS content author using Newired Editor and does not change during the execution. I.e. as stated above, we do not store nor transfer any actual data which appears on the screen of a specific person accessing the base application when the guidance shows up.
More information on how to create Journey Steps:
IMPORTANT: the information here applies in any case of deployment: if our code snippet is injected into the base application (1) or if the deployment is done through a proxy solution (2) or if Newired guidelines are rendered visible through a browser extension (3). In all the deployment alternatives, the link between the base application and Newired happens through a code snippet which communicates with the server of the base application, but is only able to recognise its structure. It cannot store nor transfer input provided by end users.