$(function () { pageContext.i18n.modTalk = 'moderation talk'; pageContext.i18n.replyToComment = 'Reply'; pageContext.i18n.modTalkEmpty = 'moderation talk is empty'; pageContext.url.getModTalk = "/comments/%25ID%25/listModTalk.json"; pageContext.url.possibleCommentRecipients = "/comments/%ID%/possibleRecipients.json"; pageContext.url.commentEdit = '/comments/%25ID%25/edit.html'; pageContext.url.commentView = '/comments/%ID%/view.html'; pageContext.i18n.commentVisibility = { 'full': 'Viewable by all users', 'op': 'Viewable by the original poster', 'mod': 'Viewable by moderators', 'opAndMod': 'Viewable by moderators and the original poster', 'other': 'Advanced visibility', 'dialogTitle': 'Comment visibility', 'selectGroups': 'Visible to groups', 'selectOther': 'Other recipients', 'selectOriginalPoster': 'Original poster', 'selectModerators': 'Moderators', 'selectAssignees': 'Asked to answer users' }; pageContext.i18n.commentMenuLabels = { 'comment-edit': 'comments.menu.edit', 'comment-delete': 'comments.menu.delete', 'comment-convert': 'comments.menu.convert' };pageContext.i18n.answer= { bestAnswer: 'Best Answer', controlBar : { accept: 'Accept', unaccept: 'Unaccept', acceptCommand: 'Accept this answer as correct', cancelAcceptedCommand: 'Remove this answers accepted status' } }; window.croles = { u: false, op: false, m: false, og: false, as: false, ag: false, dc: false, doc: false, eo: false, ea: false }; tools.init({ q: { e: false, ew: false, eo: false, r: false, ro: false, d: false, dow: false, fv: false, c: false, co: false, p: false, tm: false , ms: false, mos: false }, n: { f: false, vf: false, vfo: false, vr: true, vro: true, c: false, co: false, vu: false, vd: false, w: false, wo: false, l: false }, c: { e: false, eo: false, d: false, dow: false, ta: false, tao: false, l: false }, a: { e: false, ew: false, eo: false, d: false, dow: false, a: false, aoq: false, ao: false, tc: false, tco: false, p: false, tm: false }, pc: croles }, { tc: true, nsc: true }); commandUtils.initializeLabels(); }); Skip to Content
avatar image
Former Member

Launchpad Link to a KM document (ESS WDA)


We want to add a "link/application" to the launchpad (LPD_cust) that directly opens a file stored in the knowledge management.

In the backend transaction LPD_cust we choose as application type "KM document". Then you have to add the path to the document. As the document should be for each user a different one, we need to add a dynamic path.

I have tested the following path, which works for a certain user, but is actually not dynamic:


Is it possible to add something like "user.id" in place of the user name (in this case testuser) ?


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Dec 13, 2016 at 02:55 PM

    Hello Rainer,

    that's not so easy to answer, unfortunately.

    If your application is not FPM based and your LPD_CUST Launchpad is opened by your application itself by calling CL_APB_LAUNCHPAD_API=>READ_FOR_DISPLAY or CL_APB_LAUNCHPAD_API=>READ_FOR_CHANGE you have the possibility to provide a data provider (parameter IR_PROVIDER) of type IF_APB_LPD_PROVIDER. The latter offers a method MODIFY_VALUES which allows the modification of the launcher parameters and business parameters at runtime.

    If your application is FPM based the navigation is normally triggered by method IF_FPM_NAVIGATION->NAVIGATE. The interface IF_FPM_NAVIGATION offers a method MODIFY_PARAMETERS which allows to modify the launcher and business parameters at runtime. Since the navigation mechanism is based on an FPM event here, it's also possible to modify the launcher parameters and business parameters since they are parameters of the FPM event.

    In all other cases it is normally not possible to modify the parameters of a Launchpad entry of type 'KM Document'.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 13, 2016 at 03:52 PM

    Hello Jens,

    Thanks for your quick answer.
    I will check this back. Actually, as workaround, we are using "portal page" as application type, which points to an iView. In the iView properties we stored the information /~alias~/userhome/<user.id>/Personal Documents. So the link on the launchpad will point to this iView which calls the Personal Documents folder of each specific user. This solution does not point to a single file and the users can see all files stored in the folder.

    Add comment
    10|10000 characters needed characters exceeded