Versions Compared

Key

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

...

Widget Connector
urlhttps://vimeo.com/749166731754295162

Filter by label (Content by label)
showLabelsfalse
showSpacefalse
titleSee also
excludeCurrenttrue
cqllabel = "print" and label = "setup"

...

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 label-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 copy a template and want to modify it. 


A new customer should start out with by using the default templates on the shared tenant.
In many cases, the default offer fulfill the customer's needs.


Let's go to Business Central:
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 file 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 to the cloud print service.

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

  • The Dataset includes:
    • Context from where a label is printed (It could be an Order, an Order-Line or a Lookup-result)
    • Any Collected steps
    • ..and any customized data
  • A developer can customize the Dataset, adding, removing, or modifying values.
  • You can inspect the dataset when a label has been printed


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

Note the key-value format. Also note, how the default template uses a system of two keys for a field.

One with the value and one that contains the label for that value.

Label keys are named with Thefieldname(underscore)_"Label"


  • Designer

The designer is central to the cloud print service. It enables you to easily modify a label design without any external tools.

A label can be opened in the designer, directly from label-templates page.

It is recommended to copy a default template and then modify that to suit your needs, leaving the default templates intact.


  • Tenant

The cloud print service uses the 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 their own tenant.

If not, a shared tenant exists. A customer might begin using the shared tenant, before moving to their own tenant.

A partner can have access to all of the customers, and tenants.






...