OutSystems Go-Live Checklist

I have a checklist of tasks that I like to make sure get done before going life for a project for the first time. I have also found it helpful to go through this list periodically to ensure code quality. None of these items are particularly tricky or difficult, but they require that you pay attention and not zone out while going through the code. Here’s the list!

There needs to be a checklist for “how to regain my sanity after 10 days of a rental car”.

• Verify the the role access in each Screen’s properties are correct to the business rules.
• Use HTTPS/SSL on all pages unless you have a really good reason (such as HTML2PDF using “localhost” to retrieve a page, because “localhost” does not work with SSL).
• All Web Screens have a “Title” property.
• Go through all Actions and remove disabled logic.
• Inspect True Change for any Warnings and outstanding reminders. If there are Warnings, they should either be resolved, or if they are the result of a deliberate decision, they should be hidden. Do not hide Warnings just for the sake of getting them off the screen, they are there for a reason!
• Inspect the metadata for each Entity: do they have the “Is Active”, “Label”, and “Order By” Attributes selected as-needed? Are the Singular/Plural labels set right (yes, OutSystems does this one automatically, but it is not quite 100% perfect)?
• Use the “Remove Unused References” feature in Studio to remove the unused references from all Modules. This improves code publish times and compiled code size, which has add-on benefits.
• Make sure that the “ActiveMenuItemId” and “ActiveMenuSubItemId” passed into the Menu block on all Screens is set and correct (assuming you use them).
• Check the “Web Services Namespace” of your modules and set it correctly.

J.Ja