Unanswered questions

Each time a user runs an AIMMS app, a unique process ID is generated. I need to include this ID when exporting a data file containing multiple parameters, so that users can link each exported file to its corresponding run.Could you advise on how to programmatically access this ID within AIMMS? Additionally, is it possible to test this functionality in our local development environment, or is it only supported when connected to the AIMMS PRO environment?There is a similar topic: Reading the Jobs screen data from the PRO server into an AIMMS project. | AIMMS Community  However, I don’t quite understand how it works, as my goal is to retrieve the unique ID for each run, not just a list of jobs. If a user runs the app several times in quick succession, how can we differentiate these runs?Thanks for the help.

I got a question from a client about how to best use Git with AIMMS and how to resolve merge conflicts.This is what I came up with.I can provide some general recommendations: Make sure you are committing only relevant files  .aimmspacks are binary compiled versions for instance that do not need to be committed /backup /log /PROTemp are also normally not needed in the repository - /data is also normally not committed, unless you like to provide base cases for testing for instance This can help ensure that only git friendly files are committed and handled You can use a .gitignore to exclude generated and temporary AIMMS files Working practices to reduce merge conflicts Use multiple files for the source code This can be done in multiple ways.  For instance, you can have local libraries (which have their own folder and .ams files). You can also assign a source code file for any section or module in your project. This effectively isolates any code within that sec

Hello! I got an interesting question and thought it would be nice to share the answer here.Question: How can I make a status bar that is dynamic/flexible in AIMMS?This is how I tried it, but it didn't work:StringParameter sp_fixedStatusBar { IndexDomain: (webui::indexApplicationExtension,webui::indexStatusBarSpec); Definition: { data { ( 1, icon ) : "aimms-glass" , ( 1, color ) : "red" , ( 1, text ) : "sp_context", ( 1, tooltip ) : "sp_statusTooltip" , ( 1, procedure ) : "pr_toggleDeveloper", ( 1, state ) : "Active" } }} For those unfamiliar with the data { } construct, this may be a pitfall, since you imagine that the string parameter could be used like above - but it doesn't work that way.This construct only allows you to add data - it doesn't cater for the dynamic/flexible part.But there are two solutions. Dynamic definitionProbably the simplest solution to this, is just to switch from the data { } construct to