Workflow Email Notification pointing to wrong url

thanks smacdonald2008 for confirming. I will open one for this issue.

We are still putting a HELXP together to show use of this API. We will show it within a Workflow.

Got it working too in Java --

public void execute(WorkItem item, WorkflowSession wfsession,MetaDataMap args) throws WorkflowException {

    try

    {

        log.info("Here in execute method");    //ensure that the execute method is invoked   

        ResourceResolver resourceResolver = resolverFactory.getAdministrativeResourceResolver(null);

        //Get the FULL URL OF THE PAYLOAD in the workflow

        //Get the Assets from the file system for a test

        WorkflowNode myNode = item.getNode();

        String myTitle = myNode.getTitle(); //returns the title of the workflow step

        log.info("**** The title is "+myTitle); 

        WorkflowData workflowData = item.getWorkflowData(); //gain access to the payload data

        String path = workflowData.getPayload().toString();//Get the path of the asset

        //GET FULL PATH

        String myExternalizedUrl = externalizer.publishLink(resourceResolver, path) + ".html";

        log.info("The FULL PATH FO THE PAY LOAD IS "+ myExternalizedUrl); 

    }

        catch (Exception e)

        {

        e.printStackTrace()  ;

        }

     }

I agree, it work for me in Java or If I generate URL value using externalizer API in Java class and use it in email template as variable.

But, it does not work for OOB workflow email template at location /libs/settings/workflow/notification/email/default/en.txt

where its using $ {host.Prefix} for URL.

For me its product issue since its only with OOB emails.

Do you know or can you check how $ {host.Prefix} variable value is calculated and passed to this template then we can figure out which configuration is actually responsible for host.Prefix wrong value

F

Here is a HELXP that shows using this API in a Java class --

Adobe Experience Manager Help | Creating an Adobe Experience Manager 6.4 custom workflow step that uses the Externalizer…

There is a video too in this HELPX that shows this API working.

ok i saw this before but it does not answer my question why OOB email template host.prefix variable does not have correct value.

Can you check with your team on this since its Adobe OOB email and back end class who call this template to trigger email.

this will help me understand how $ {host.Prefix} variable value is calculated and passed to this template then we can figure out which configuration is actually responsible for host.Prefix wrong value

There is a bug ( when trying to use it within an email template) as customer support stated.

This article is for ppl whom want to know how to build a solution with this API and see it running.

When we were investigating this - i saw we had no HELPX Quick Start for this API - that is and end to end to quickly get it working.

got it thanks

I dont understand why this thread was marked Answered though its pending further investigation by support or original issue for which this question was created does not resolved yet.