on 09-22-2014 11:42 AM
Hi, all.
I've tried that the original-fiori app and the copied-fiori app coexist same gateway.
But I'm in trouble that the copied app (customized) run with original source code.
Though same scenario is run on copied-app, I think the logic of customized code don't work.
For some reason, it works in accordance with my expectation by adding URL query of sap-ui-debug...
Procedure I've done is following.
1. Download original fiori app(Approve Requests).
2. Customize source code at Eclipse.
3. Upload WebContent by another name on 'se38-/ui5/ui5_repository_load'.
4. Config at 'lpd_cust' & launchpad manager.
Customizations is following.
1. button handling of xx.controller.js
2. UIComponent library id 'cross.fnd.approve.requests' > 'cross.fnd.approve.requests.custom'
3. Library id changes reflect to all source (xx.xx.js, xx-dbg.xx.js, xx.xml etc)
Someone, please advise if you succeed to try like me.
Thanks.
Tags edited by: Michael Appleby
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Masa,
Thank you for a clear answer.
I wrote at my first posting that the customised code ran by addition URL query of 'sap-ui-debug=true' as I expected.
If that query omitted, the code does not run.
(it seen like original code run.)
Files for debug and not for debug are same contents.
I don't know what should be suspected.
Thanks regards.
Please mark this Discussion with a Correct Answer and Helpful Answer where appropriate. See http://scn.sap.com/community/support/blog/2013/04/03/how-to-close-a-discussion-and-why Even if you discovered the solution without any outside contributions, it helps others to understand what the solution turned out to be.
Regards, Mike
SAP Customer Experience Group - CEG
Hi Mike,
I'm unable to close the discussion/mark as answered as I didn't start it.
The issue I had seemed to be the same as described by Makoto.
To offer a little more detail in my own case. I copied the Fiori MyTimesheet App to a Z-version (extensibility wasn't appropriate) and applied changes to the views/controllers; these changes where not visible at runtime as the original component-preload.js file still contained the original standard code; the changes where visible in debug mode as the component-preload.js file is not loaded in debug mode.
Hope this is helpful for someone else.
Regards, Neil
Hi Neil,
I am into customer incident handling , and for one of the customers,in Team Calendar, the same issue happens: when I pass the URL parameter the code works fine.
I understand from the above conversation that it happens because the component.preload is loaded at the runtime.
But how do we correct it? is there a way? Instead of passing the parameter everytime.
Please guide.
Regards,
Priya
Hi Priya,
I've been away on leave, so only just saw this.
As our MyTimesheet application was a customer copy I resolved the issue by commenting out the code in the component-preload.js file.
I believe the main purpose of this file is to improve the performance/response times of the application, although in our case the application performs well for 2,500 users without the file. As an alternative the code in the component-preload.js file could be updated to reflect your changes.
Hope this helps,
Neil
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.