With Dynamics AX 2012 R2 CU7, a new Task Recorder has been released. The task recorder will allow you to record your business processes inside AX, generate a package, and upload them to Lifecycle Services (LCS).
It is generally suggested that you run the Task Recorder and AX client on the same server as your AOS to build the recordings. Many organisations restrict access to the AOS, so this is not always possible. When you are done recording the business processes and wish to generate package to upload to LCS, you are supposed to click on the ‘Build package’ button in the Task Recorder.
Unfortunately the error handling is limited in this version of the product. If the build process has an issue, quite often the button can be clicked, turns orange, and then returns nothing. The AOS server is attempting to build the package via a batch job, but if you are in a distributed environment, it’s quite likely the build is failing as it tries to find the recorded tasks. Check the Parameters form and ensure that the tasks are saved to a shared network location that both your AX client and the AOS have full access to.
The above is not a good location.
When the Build Package process is started successfully, you should see this message:
When the process completes, an axbpm file will be generated in the file path specified in the parameters screen. Be aware that this process can take a long time depending upon network and processor speed. I have seen small jobs take 15 minutes to complete. Progress can be viewed in the Batch job form under System Administration > Inquiries > Batch jobs > Batch jobs.