The number one thing slowing down a solution to a problem is insufficient information. The best step you can take prior to contacting Flex Support is good documentation. The back and forth required to understand problems more deeply will slow things down. Document the problem thoroughly and the solutions will come much more quickly.
Document the problem
The more information you collect about the problem, the faster Flex can provide a solution.
- Document the error
- Screenshots of error
- Text from the error, in full
- PDF/screenshot of results in Flex or connected apps
- Your one line description of the problem
- Document the steps and items involved
- The url of your Flex instance
- Location where problem occurred (Where would Flex Support go to recreate this?)
- Actions just prior to the error (How would Flex Support recreate this?)
- Results expected versus results observed (What you thought should happen and what did.)
- Elements affected in Flex (Where can Flex Support see the specifics of this?)
- Forms affected in Flex or connected apps (Where you thought you'd see the data and where you did.)
- Document the efforts to resolve
- Actions you've tried
- Flex resources you thought would solve the problem but haven't
- Outside or connected apps resources you thought would solve the problem but haven't
Submit a Support Ticket
Remember, the more information you provide, the faster Flex can provide a solution.
- Submit a ticket
- Summarize the problem
- Include all the documentation above