Nestlé WebAR Platform (WARP) Integration
Nestlé WebAR Platform (WARP) integration is a custom integration that enables Nestlé and their partner agencies to publish XR projects built with Zapworks Designer, Mattercraft and Universal AR to the Nestlé internal hosting and serving infrastructure, WARP.
Access to this functionality via Zapworks is enabled on a per-workspace basis and is not available to customers outside of Nestlé workspaces.
Prerequisites
In order to use this functionality, there needs to be a request to the WARP and Zappar platforms.
- For Business Owners: Follow the activation process here: WARP Activation Process
- For Agencies: Contact your business owner to fill up the request form for Zappar: WARP Activation Process
- For Issues: Open a ticket here: Incident
Project creation and WARP integration
The Zapworks integration to Nestlé WARP is enabled per-workspace. In order to confirm whether the WARP integration has been enabled on your workspace, create a project and if it is available, you will see this clearly labelled UI component on the project overview page.
If the integration does not appear to be available, please contact support@zappar.com who will be able to investigate.
Project information setup
On enabling the Nestlé integration, you will be prompted with a modal that allows you to store (for easy access) the following important information relevant to the Nestle WARP publishing process:
| Field | Description |
|---|---|
| Repository URL | Project repository location |
| DigiPi number | Project identification number |
| Notepad | Free text field with pre-populated entries: Project owner (name and email), GA tag reference, Cookie Banner (OneTrust) reference |
This data is then saved on the project overview page. Note that you can use the markdown format bold (**bold**) if desired to distinguish between titles and fields.
If you do not have all the information at the start of the project, these fields can be updated at any time by clicking on the Edit info button (shown in the graphic below).
We recommend coordinating getting this information with Nestlé early in the product development process so you don't need to do so when approaching the project deadline.
Project development
The content development stage is exactly the same for projects published to Zappar's infrastructure or Nestlé WARP. You should build your Zapworks Designer, Mattercraft or Universal AR project as normal.
Once you have published the project in the Zapworks platform at least once, you will be able to push those published files, a project version, to Nestlé WARP.
Publishing to WARP
Your published version is now ready to push to Nestlé WARP. Click the button on the project overview page to prompt the modal.
The following fields are required:
| Field | Notes |
|---|---|
| Repository URL | This is pre-filled if inputted earlier. |
| Environment | Either Staging or Production. |
| Username | Discoverable from WARP. |
| Access token | Discoverable from WARP. |
| Zapworks version | Dropdown of all published versions. |
| WARP version name | Written in the$X.$Y(.$Z) format, for example 1.0.0. |
| Change log entry | A description of changes made since the last publish. |
Once completed, click Push version to WARP. If successful, you should see the project files in the WARP repository, along with the changelog. You will receive an email from MSEToolchainService@es.nestle.com with the build status once complete.
Your access token from WARP can only be viewed once, will not be stored in Zapworks and is required each push to Nestlé WARP. We strongly recommend saving this in your preferred password manager.
Updating projects
If you make any subsequent changes to the Zapworks project, you will need to repeat the publishing process in order for those changes to be updated in the Nestlé WARP infrastructure.
Production deployment
Publishing to production in the Nestlé ecosystem will require an approval from a business owner. In order to deploy to production and make the project live at your chosen URL, you will need to coordinate this with Nestlé via ServiceNow. We have added a hyperlink on the Zapworks project overview page to do so, although this step is handled outside of the Zapworks ecosystem.