QLingo (Advanced Logic) Workshop

Plan files store a campaign's logic and are required for all campaigns. These files define the data sources, tables and fields and how to use those to calculate Content Object/ADOR's values that appear on the variable templates within a print and transmedia campaigns. Campaign logic (QLingo) can be as simple or as complex as needed. The standalone application, uPlan, can be used to edit plan files to fix logic without having to use uCreate or the Circle Plan editor. When complexity is key, uPlan provides flexibility that allows for connecting to multiple local and remote data sources, several data tables with specific queries and filters, advanced logic formulas, and building custom functions or integrating those functions with other applications (called extending QLingo).

Workshop Required Software: Adobe InDesign, XMPie uCreate, uPlan and, if applicable, access to the uProduce Dashboard.

Allotted time (based on your purchase) for these practices range from 2 to 8 hours.

uPlan/QLingo Hands-on Practices:

 

 

Back to ILT Workshop Links

Hands-on Practice 25: Creating Campaign Logic with uPlan (Basics)

This practice walks through using the uPlan application to build a plan file that contains basic and intermediate level campaign logic by implementing a recipient data source, along with an additional related data source. Beginning with concepts, terminology, the interface, workflows and previously used features are reviewed.

Audience: Data or logic programmers benefit most when available. Other variable data production designers that work with logic are encouraged to attend.
Learning Prerequisite: Basic SQL and other data programming skills are helpful. Must have completed Practice 1 and optionally, 3.
Practice Takeaway: How to edit and use a plan files.
Estimated Effort: 1-2+ hours, depending on Q&A.
Learning Materials: TBD

Learning Objectives:

  • Review the uPlan interface and plan components 
    • ADOR Objects (aka Content Objects)
    • Recipient Objects and Filters
    • Data Source Objects and Tables
    • User Views
    • Variables and Audiences
    • Functions
    • Linking assets
  • Review the typical workflows for plan files, their creation and how they are used.
  • Modify an existing plan file based on requirements.
    • Review the modifications needed
    • Download from uProduce
      • The plan file to edit
      • Data to use with the plan
    • Review the plan's components (ADORs, variables, etc.)
    • Add a recipient filter (SQL query) 
    • Create and use a plan variable
    • Modify other rules and review/use QLingo functions
    • Generate proofset(s)
    • Discuss how to use plan files and proof sets

 

 

Back to ILT Workshop Links

Hands-on Practice 26: Creating a complex plan file

This practice explores more complex features and functionality not available in other plan editors. Here a plan file is created from scratch using multiple data sources. 

Audience: Data or logic programmers benefit most when available. Other variable data production designers that work with logic are encouraged to attend.
Learning Prerequisite: Basic SQL and other data programming skills are helpful. Must have completed Practice 1, 3 and 26.
Practice Takeaway: How to build a plan file from scratch using multiple data sources. 
Estimated Effort: 2+ hours, depending on Q&A.
Learning Materials: TBD

Learning Objectives:

  • Review campaign objectives, the data supplied and what is needed for the Content Objects/ADORs for all campaign touchpoints.
  • Create a new plan file using two data sources and build Content Objects based on the campaign's requirements.
    • Using the Getting Started plan wizard
    • Review the wizard created objects (use only recipient data)
  • Add another data source.
    • Use the wizard to add a data source, explain the differences
    • Create a user view for the additional data source
    • Review and discuss the SQL required
    • Create ADOR objects or Table Object 
    • Discuss or use User View QLingo functions
  • Create and use variables (as needed)
  • Create and use a custom function
  • Discuss dials, insert expression, and other features.