This thread was migrated from an old forum. It may contain information that are no longer valid. For further assistance, please post a new question or open a support ticket from the Customer Support portal.
Hi Guys,
I am new to Kony Visualizer. My team has to build the UI and write the code for validations and transitions. While another team would integrate it to Mobile Fabric.
What is the best way to package the code for delivery to the other team. Considering there will be multiple forms for multiple journeys. Should i create a component for each journey? or just export all the forms for the journey and send it.
For Example, Sending Money is a journey which would include multiple forms like input form, confirmation form and transaction receipt form . How can we package the whole thing?
What is the best to do this. Please link in docs or articles present about this.
The best way for this requirement is to segregate the UI & Controller's , invoke the UI objects though java script in Pre-AppInit.
In this model , UI team can develop screens and Development team can create necessary objects (POJO references to UI elements), MF team will invoke services and fill the objects with data.
A sample app is created for your understanding. (MF invocation is not included in sample app).
The app explains how to invoke UI elements through code , this will make UI and javascript modules independent to each other.
I took a look at the document and the app , thanks a lot for sharing those. However, i am still confused in some areas in which i would need your help
Reference Architecture vs Free form Javascript : I have been reading about Reference Architecture and according to the documentation , we should ideally follow this architecture. But most of the components and sample apps from kony ( including the one shared by you ) are built in free form. Can you please share the example in Reference Architecture form.
I am getting confused mostly in the part of Object Model or the model aspect of the architecture. As i believe (if i am not wrong) this is the point of contact between the front end developers and the backend developers .
My team has to develop the ui and add basic validations events, transitions and just provide proxy/stub controllers while the integration is to be taken care of by another team. It would be great if you can help me setup a sample app for this to understand the structure of the deliverable we need to send off to the other team.
Also, is it possible to have a call with me ( hangout or phone ) to discuss this ? I would really appreciate your help with this.
The agenda of the document and the shared application is to give you an idea to differentiate dependencies between UI & Controller , the explanation has nothing to do with Reference Architecture & Free Form , i can confirm irrespective of what is used the model remains constant.
Please refer kony documentation for more detailed explanation on Reference Architecture.
Point 2 , your understanding is right, Object Model is the model which withholds the UI values at the controller end and this is same across all platform hence in Kony.
Point 3, As i shared in example , you & your team develop UI, Controller's (add validation in code) , Events (Initialise functions as part of controllers), Postshow method , once another team shares you the code you can integrate those JS files into your project. however please remember you will be responsible for naming conventions as you are working at integration end.
I got that we have to develop the UI and setup the controllers , but the integration is to be done by another team whom we have to deliver the code . So should the object model part be done by us or the team which integrates it to the mobile fabric.If it is to be done by the other team, then what would our code look like for example - if we put a chart , the model of that chart or the model of a segment is to be decided by us or should be done by the Integration team ?
Thanks for answering @Jessicv Russell . I have given you a lot of trouble with my question. Please help me with one last question . As how should be the output from our end so that the other team gets the best idea of how the model will be (once we give them the ui design with stub controllers ) and apart from validations and other functionalities, what should be the other things ( regards to object model ) our team should add ?.
@Rose Butlew , I'm happy to answer any number of questions as long as you get the best right answer,
your need to share the names of UI elements like text/ label where ever you want to display object values returned from the Mobile Fabric Response Output.
This way you will restrict the other team to follow the naming conventions which inturn will form the full fledged output starting from UI to backend.
My advise is not to share anything else to keep a full control of UI and controller stubs , simply share the naming conventions , collect the object / POJO js files and link to the UI through controller.
Right . I think i have a better understanding of this now. Only one thing which i am still not clear of is the POJO js file, is it a file containing the getters and setters of various UI elements ? can you point out the file which has the POJO functions in the app you shared and how (and where) are these functions used. That would serve as a great example and be of great help.
Thanks @Jessicv Russell for patiently clearing my doubts . If you can provide me with a sample app based on Kony reference Architecture showing the whole process ( the UI , model , POJO files and the MF connection ) it would be of great help,
Also i was reading about Kony reference architecture , when i came across a paragraph stating that
"Developers on the front-end app can build objects that provide mock services to the app. That is, developers can create models to use in the front-end app that simulate the interaction that the front-end Kony Reference Architecture app will have with the backend Kony Fabric app when the backend app is complete. Using these mock services, both the front-end app and the backend app can be under development at the same time."
Can you help me figuring out how to create these models to simulate the interaction .A sample app showing these processes would be of great help.