Hi All.
I have been away from B4X for a number of years.
I am looking at creating a new app, initially for B4A, but later for B4i too.
The app will be a job dispatching system. A job will be sent to the app and the user will complete the job, recording various information on what is done, and then capture a customer signature, and then send the information back to our server. The main functionality of the app is not a problem (I created a similar app many years ago with B4A), however there is one issue I need advice on.
There could be many different types of 'job' and each type of job would require different types of information to be recorded, added to this, the information required could change fairly frequently and new job types added.
I had initially thought to be able to dynamically create the information capture page using a JSON definition file sent with the job from the server, however I have read many times on the forum from @Erel that it is NOT the correct way to build a page using only code (especially for B4i), therefore my question is how can I correctly handle such situations where different information needs to be captured? I do not want a hard coded view for each job type that would require an update to the app every time some additional information needs to be captured or a new job type added.
I look forward to hearing your suggestions.
I have been away from B4X for a number of years.
I am looking at creating a new app, initially for B4A, but later for B4i too.
The app will be a job dispatching system. A job will be sent to the app and the user will complete the job, recording various information on what is done, and then capture a customer signature, and then send the information back to our server. The main functionality of the app is not a problem (I created a similar app many years ago with B4A), however there is one issue I need advice on.
There could be many different types of 'job' and each type of job would require different types of information to be recorded, added to this, the information required could change fairly frequently and new job types added.
I had initially thought to be able to dynamically create the information capture page using a JSON definition file sent with the job from the server, however I have read many times on the forum from @Erel that it is NOT the correct way to build a page using only code (especially for B4i), therefore my question is how can I correctly handle such situations where different information needs to be captured? I do not want a hard coded view for each job type that would require an update to the app every time some additional information needs to be captured or a new job type added.
I look forward to hearing your suggestions.