6th Day Innovations
Dynamic Document Creator
FAQs / Help
Please see some common questions and their answers below.
FAQ's
Can I create multiple documents for the same record?
Yes, Absolutely.
Just create a 2nd Document record for the same table. Just ensure you create a separate Business Rule or UI Action with the appropriate conditions. Also make sure your order of operations is correct for the documents.
Do the Document records have to be in the Global Scope?
Absolutely not!
You can put them in any scope you like. Be careful with Cross-Scope permissions.
Are there any 3rd Party Libraries in use for this application?
No!
Everything is contained within ServiceNow from OOTB API's and custom written code, but no custom libraries.
What versions of ServiceNow does this support?
We began development of this application on Quebec and have updated it to Rome, San Diego, Tokyo and Utah.
We have just recently put it in the ServiceNow store and it's currently certified for Vancouver, WashingtonDC and Xanadu.
Do I have to create a global script includes for the Zip to work?
Unfortunately yes.
With our application being scoped, we do not have access to run the "Packages" call that is needed to create the zip file. Maybe one day we can create a way, or SN will allow the "Packages" call to happen from within a scoped application.
When Creating a Business Rule, why do you recommend "Async"?
Great Question!
Previously we had more control over the creation of Business rules and we had more on-the-form details. Now we no longer control Business Rules, so we need to specify here.
The main aspect is system performance. Because we have a Pre-Run Script and a Post Run Script as well as an Event that can be triggered, if run in a Before Business rule, all of that has to process before the current record can be updated.
We have seen people run multiple integrations during this process, we have seen long scripts that need to be run that update other records. When you update other records, those before BR's need to run and After BR's need to run, and if those BR's update other records, then those BR's need to execute.
And all of that needs to execute BEFORE your screen is released.
Doing it 'async' allows all of that to happen in the background as the system has time. It allows for the screen to be released and is easier on system performance.
HELP / Common Issues
My Document will not create.
A few common issues we've seen:
1. Check your Business Rule.
Ensure it's created properly. It needs to be run on the same table as your document record. You need to make sure it's got "On Insert" or "On Update" selected.
Ensure the script in your Business Rule, matches the script we provided to you on the Document record.
Ensure your Business rule is set to active.
2. Check your Scheduled Job.
Ensure it's active, and the script matches what we have provided to you on the Document Record.
Also, If you added conditions to the scheduled job for running, make sure the conditions are met to run the job.
3. Check your UI Action.
Ensure it's set to active and on the correct table and the script is set to what we have provided to you on the Document record.
4. Check your images.
Some images cause errors when creating PDF's. Sometimes, using some images, the PDF document will not create. We believe this is an issue with the PDF api that is being used. Try to replace the image being used.
5. Check your Scripting...
While creating the file name, or the pre-run script (if being used) or the run script; ensure you have no typing errors when it comes to scripting.
I want a longer file name!
Before Windows 95, Windows only allowed file names that were eight characters long, with a three-character file extension — commonly known as an 8.3 filename. Windows 95 abandoned that to allow long file names, but still limited the maximum path length (which includes the full folder path and the file name) to 260 characters. That limit has been in place ever since.
So while Windows may allow for longer file names, by default, ServiceNow limits the file name length by the length of the "file_name" field on the "sys_attachment" table.
We only allow for the file name to be as long as the file_name field.
My event will not trigger.
Because this is a scoped application, you need to be cautious of Cross-Scope permssions.
This application may not have permission to trigger events.
You can always create events within our scope and use those if necessary.
Still have a question?
Please send us a message and we will get back to you!
Contact Us
