Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Excerpt

In this video, you will be introduced to the terminology we use used for the Cloud Print Solution service.


Widget Connector
urlhttps://vimeo.com/749166731

...

Excerpt
hiddentrue

Agenda:


  • Label-Template
  • Template Handler
  • Dataset
  • Designer
  • Tenant


In this video you will be introduced to some of the terminology used for the Cloud Print Solution 


  • Label-Template

The system comes with a set of default label-templates

We call them templates as they are known as "templates" in the designer.

Templates represent, among other things, the design of the label.
The default templates are documented here on Docs. You can see an example with real-world data and a mock-up with placeholders where each element's name is visible. 
This is useful if you plan to modify a template. 


Let's go to Business Central to have a closer look at templates.:
Go to "Mobile Print Setup" > Select Templates

There is where you set up the templates you want to use.

Templates are named with their function and their size. For example, "Item Label 2x1" means this is an "Item Label" and that it is 2 inches wide and 1 inch high.

It also has a Display name, so the mobile user can have a friendlier name on the mobile device.

"Template path" represents the path of the template in the designer.

"Available to" tells you whether a template is available to all - or only specific mobile printers.


  • Template Handler

 
The system comes with a set of default Template Handlers.

They make it possible to share and reuse logic, step-collection and data mapping between templates.

Say you create a copy of an existing template, setting the Template handler to the same as the original, makes you able to reuse the same logic for your template.

A developer can create code, that modifies how template handlers work


  • Dataset

The dataset is an intermediate key-value format we use to ease the transfer of data from Business

Central 

Dataset and design are independent of each other, meaning the same dataset can be used by any design, e.g, different label sizes.

  • Print request contains mainly the dataset
  • Dataset is customizable with events, so you can add/change values in it
  • The dataset can include

    Central to the cloud print service.

    The dataset is generated as a result of the template handler and the context used when printing a label.


    • A developer can customize the Dataset, adding, removing or modifying values.
    • The dataset typically includes:
      • Context (Order, OrderLine, Lookup-result etc.)
      • Collected steps
    Customized data. See Print Label and Print Label for examples
      • Any customized data
    • Dataset examples for each default template
    is available at Standard Label Template Designs   
    • , are available on Docs.


    Let's go to Business Central:
    Go to Mobile Document Queue > Find an entry for a Label print > Select "Print Log" > Select Log > 


    • Tenant

    The cloud print solution uses the Tenant concept multi-tenancy principle to isolate customers, their templates, and processing from other customers.

    If a customer wants to make changes to templates - they must have a separate their own tenant.

    If not, a shared tenant exists. A customer might begin using the solution cloud print on this tenant, before moving to a separate tenant.

    A partner can access several customers tenants.


    ...