"hcpdeploy": {
"account": “<your account name. For example, 'myaccount123' in http:/webide-myaccount123.dispatcher.hanatrial.ondemand.com/>”,
"name": “<a unique name for the app, usually it is the name of the app in the workspace in lowercase without dots>”,
"entryPath": “<the relative location of the component.js file to the root folder of the app. For example: webapp >”
}
{
"applications" : {
}
}
"FioriObject-action" : {
"additionalInformation" : "SAPUI5.Component=<application namespace> “,
"applicationType" : "URL",
"url" : "<path to MyFioriApplication . MyFioriApplication name as it is in the Web Ide workspace >",
"description" : "<The description for the application >",
"title" : "<the title of the tile>"
}
Object | Description |
FioriObject-action | An identifier used later by the application. It must be constructed from two identifiers with a dash, not “FioriObject display” or “FioriObjectdisplay”. |
additionalInformation | The namespace of the root component of your Fiori app. You can copy it from the Component.js file of the app. It will be in the declaration of the component. For example: "return UIComponent.extend("my.target.app.Component", { …" make sure to copy without ".Component" |
applicationType | The application type for SAPUI5 applications is always URL. |
url | The URL property is the path of the applications relative to the fioriSandboxConfig.json file. In my example it will be "url": "../../mySourceApp" |
{
"path": "/test-resources/sap/ushell/<application name in Web IDE workspace> ",
"target": {
"type": "application",
"name": "<the unique name for the app, as it was defined in its .project.json file of the application>"
}
},
{
"path": "/<application name in Web IDE workspace > ",
"target": {
"type": "application",
"name": "<the unique name for the app, as it was defined in its .project.json file of the application>"
}
},
var oCrossAppNav = sap.ushell && sap.ushell.Container && sap.ushell.Container.getService("CrossApplicationNavigation");
var href_For_Product_display = (oCrossAppNav && oCrossAppNav.toExternal({
target: {
shellHash : "<the target app key configuration defined in step 4, e.g. FioriObject-action>"
},
params: a map of parameters to be forwarded to the target app
})) || "";
That’s it!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
44 | |
22 | |
17 | |
15 | |
11 | |
9 | |
8 | |
8 | |
7 | |
7 |