Change Request Form

Change Request Form

Please submit this form with as much detail as possible including any artwork mock ups, design elements, example spreadsheets, detail on work, field mapping etc. If there is not enough detail the team may come back to you and ask you to resubmit with more detail, which may delay the quoting process.
Before submitting your change request, please familiarise yourself with our Change Request Process, so you are aware of timelines and the steps in ensuring a successful deployment of your change.
Contact Details

Please provide contact details of both the person requesting the change and that of the person who will need to approve the change request, if different to the person requesting.
Company Name*
Contact Details Of Person Requesting The Change*

First NameLast Name
Role*
Email*
example@example.com
Contact Details Of Person Approving Change (If different from the above)

First NameLast Name
Role
Email
example@example.com
Change Request Details
Title Of Change Request*
Please provide a brief descriptive title of the change request
Date Of Request*

MonthDayYear
Date
Preferred Delivery Date and Anything Detail Affecting the Reason for that Date.
Please note - we can not guarantee we will be able to deliver on this timeframe. Only once the quote is approved can we provide timelines but dates and what affects these dates assists in the planing process.
Desired Delivery Date Of Change Request*

MonthDayYear
Date
Reason For Change*

New Template RequestNew Theme RequestAdjust Existing TemplateAdjust Existing ThemeAdd/Change A Business Rule/Trigger Event/Configuration of Your Data ImportAdd/Change How We Send You Data eg: move to API from spreadsheet importAdd an IntegrationAdd Electronic Shelf LabelsAdd Retail MediaOther
Template Or Theme Name *
What is the name of the template or theme you want to update?
Is the template change for Paper Tickets or ESL or both

PaperESLBoth
Is there any configuration considerations with adding this Theme?
Do you have any business rules associated your themes? If so please specify and relevant changes
Please describe your current rule/trigger/config as it is now and then how you want it to behave instead. *
Describe what is used, what it generates, what is the new change to this.
What ESL Provider have you chosen?*
Name the Hardware provider you have chosen, ticket multiple if you are running multiple
Will you be running a hybrid store both ESL & Paper ticekting?*

YesNoNot sure yet
Please list the ESL device size(s) you are going to be using.*
Please indicate the type of data that will be used in this integration*

Product (eg, department, brand, description, unit of measure etc)Price (current and/or future dated price changes)Promotions (promotion and offer information with stat/end dates eg; multi buy, % off, campaigns)Planogram (to enable smart print sorting for store users and accurate ticket copies per store)Other
Select the method(s) available to Last Yard for connecting to your data source(s*

Open Database Connectivity (ODBC) (eg SQL server or other traditional database)Rest API (cloud)Rest API (internal, behind a firewall)Your system(s) can POST spreadsheet data to the Last Yard APIYour system(s) can POST indidivudal records tot he Last Yard APUI am happy to manually drag and drop my CSV and/or XLXS files into Last Yard whenever data changes
Is your data source the same for all stores (hosted at head office) or unique to each store (in-store connection)?*

Single data sources at ahead officeData source in each storeOther
Priority*

CriticalUrgentHighMediumLow
Impact On Business Creating Need For Change *
Summarise why this change is required, the impact it has on business and how the above priority relates to this.
Area Of Change*

Head OfficeStore LevelTemplates & ThemesData importBusiness rules/Data TriggersOther
What Programs, If Any Are Involved In This Change?*
EG; POS, Planogram
Please Describe The Expected Outcome/KPI*
Please Upload Any Images and Data Files Relevant To This Change

PDF Artwork, Example Data Files
Cancelof
What Would Be The Preferred Strategy In Event That The Change Fails*

Roll back to the latest versionKeep feature in place and bug fix
What Process Will Be Used For Acceptance Testing (UAT)*
Define how this would pass UAT acceptance testing.
Should be Empty:

Change Request Form

Contact Details

Change Request Details