DBC: Chili - Backoffice

Accessing GraFx Publisher

To access your GraFx Publisher environment, go to https://chiligrafx.com and enter your login information.

You will land on the following page where you can access Chili GraFx Publisher by clicking the Chili GraFx Publisher icon.

Once you enter Chili GraFx Publisher, you will have three categories within the header area, Resources, Settings, and System.

• Resources - Most data in CHILI Publisher is managed as resources. This includes assets, documents, and fonts.
• Settings - Where you will administer specific settings your documents will inherit. This includes Barcode Types, Document Constraints, PDF Export Settings, and Image Conversion Profiles.
• System - Can be ignored, as we will not do anything within this area.

RESORUCES

Once RESOURCES has been selected you will be presented with three categories, Assets, Documents, and 3D.

Assets

Assets

The Asset Management module is a basic repository for your assets (images, pdfs, ...). It is not meant to be a full Digital Asset Management Solution, but rather provide basic storage for images to be used in CHILI Editor.

FOLDER STRUCTURE: Assets \ Customer Number

• The customer number is the DB Commerce customer number found under Work with Companies.
• All your art files will reside in the folder under that specific customer. If the image is background art and not anything selected by the end user you will house this in the company folder.

• In some cases you may find that you want to present your end user with a specific selection of images for an item. First, you want to find out if the images will only be used on your Chili items or does the customer want to give their users the opportunity to download these files and use outside of the DB Commerce Platform?
  • If the images are only going to be used on your Chili Items, you will want to use Chili Assets.
  • If the customer wants to give their users the opportunity to download these files and use outside of the DB Commerce Platform, you will want to use DB Commerce Assets. An example of when you may want to use DB Commerce Assets is if your customer has logos. Maybe the customer allows someone within their Marketing Department to upload the company logos to the DB Commerce asset area. These can then be available to the users on that site so they can use them in within their Chili item (available when customizing an item) or download them and use them else-ware (available in the navigation area of the DB Commerce site).

Chili Assets Used on a Specific Item

FOLDER STRUCTURE: Assets \ Customer Number \ Item Code

• The customer number is the DB Commerce customer number found under Work with Companies.

• All your art files will reside in the item folder, that will be used for the end user selection. There may be some images that are used across multiple items, for example Employee Photos. In a case like this we suggest setting up another sub-folder (Assets \ Customer Number \ Employee Images) that would house these images and could be used across multiple items for that company.

  

Documents

Documents

This is where all of your Chili files will be stored. you can organize, access, and manage them from there anytime.

There are up four folders you may see under the Documents area.

• 00 Chili Support - Possible copies of templates when Chili Support is helping to diagnosing an issue.
• From InDesign - Documents imported from InDesign, that should be moved or assigned to the correct folder when imported.
• items - Chili Documents that will be associated with a DB Commerce item code
• user_temp - User specific files that will be imported for further investigation by DB Support if needed.

All your Chili Documents should reside under the items folder.

FOLDER STRUCTURE: Documents \ item \ Customer Number

• The customer number is the DB Commerce customer number found under Work with Companies.
• All your Chili Documents will reside in the folder under that specific customer.

• Once you select a customer folder, you will begin to see your Chili Documents within that customer. Chili Documents should be named according to the DB Commerce Item Code found under Work with Items.

  

Fonts

This is where all your fonts will be stored that are used in you Chili documents. (Keep in mind to check your font supplier for the right license. Supported font types are .OTF and TTF. Best results are generated with .otf fonts. They are consistent on PC / Mac / CHILI Publish.)

FOLDER STRUCTURE: Fonts \ Font Name

• All fonts should be stored by Font Name. Any specific styles will reside in that font folder.

Workspaces

Workspace are the end users view of the Chili Editor within DB Commerce. You have the ability to lock down specific tool-bars, change colors to the canvas, borders, bleeds, etc. Workspaces cannot be changed from within the Backoffice. You need to edit and save workspaces from within the editor.

View Preferences

View Preferences define the look and feel of the document for the end user. This is where all kinds of settings can be set such as measurement units, page border visibility, frame highlighting, grids and much more. View Preferences cannot be changed from within the Backoffice. You need to edit and save view preferences from within the editor.

3D

This can be ignored as we will not use 3D within the DB Commerce platform.

SETTINGS

Once SETTINGS has been selected you will be presented with four categories, Document Settings, Export Settings, Users, External Systems.

Document Settings

Blank Doc Templates

This can be ignored as this is not used within the DB Commerce platform.

Image Transformations

This can be ignored as this is not used within the DB Commerce platform.

Barcode Types

This is where you will set up the presets for your QR Codes.

What is a QR Code?

QR Code (abbreviated from Quick Response Code) is the trademark for a type of matrix barcode (or two-dimensional code) first designed for the automotive industry. More recently, the system has become popular outside the industry due to its fast readability and large storage capacity compared to standard UPC barcodes. The code consists of black modules (square dots) arranged in a square pattern on a white background. The information encoded can be made up of four standardized kinds ("modes") of data (numeric, alphanumeric, byte/binary, Kanji), or through supported extensions, virtually any kind of data.

Source: Wikipedia

Setting up a QR Code

ODT Import Settings

This can be ignored as this is not used within the DB Commerce platform.

Structured Text Import

This can be ignored as this is not used within the DB Commerce platform.

Document Constraints

CHILI Publisher is built around the concept of giving users full or limited access to the same document. This concept works all the way through up to the smallest element, a document frame. The restrictions you can apply, are called constraints. Constraints can be set on different levels. From the Library (top level folder of your documents) down to the frame of a document. In between restrictions can be set to Documents, layers and objects. Restrictions on the top level can be inherited down to the document, layer and frames. The restrictions you can apply, can be saved in sets, and applied to other documents. e.g. a user can never move objects, but always edit content. Usually, constraints are configured inside the actual CHILI Documents. But in the BackOffice it is possible to create pre-determined rules with constraint settings. When opening a document in the Editor, these rules can be applied automatically.

In main navigation, go to Settings > Document Settings > Document Constraints

Identically to other settings, you will get a list of definitions on the left and a form on the right to edit the selected setting.

In the set / definitions, you can apply multiple constraints, each on a different level.

You can choose between document, pages and layers.

For each level, you can then set the constraints (e.g. Lock movement, ...) and save the changes you made. DB Commerce already has three pre-created options when your environment was set up, so this may be an area you never touch.

Export Settings

PDF Export Settings

PDF Export settings is a list of pre-defined settings for the PDF-output. You can create new groups of settings. These settings can be used to generate PDFs using this set of preferences.

General

In the general part, you can change the name of your setting.

Document

PDF Info

This part contains meta-data to be written in the PDF document. You can have some information about the document filled in automatically with the use of patterns.

HTML Export Settings

This can be ignored as this is not used within the DB Commerce platform.

IDML Export Settings

This can be ignored as this is not used within the DB Commerce platform.

ODF Export Settings

This can be ignored as this is not used within the DB Commerce platform.

Image Conversion Profiles

With Image Conversion Profiles you can specify a profile by which images are to be transformed. They can be used to do some (limited) optimization of PDF output (but mostly for low res files), but the main purpose is to provide image output for documents and assets, used to generate image ouptut of CHILI documents (as a separate output format, or for embedding in other output formats such as the mobile reader in design mode).

Settings for JPG

Settings for PNG

Users

This can be ignored as users are managed in a different area. This will eventually be deprecated within Chili.

External Systems

This can be ignored as we will not use any of these options within the DB Commerce platform.