cancel
Showing results for 
Search instead for 
Did you mean: 

Issue while referring the Master Page from a MasterForm (Fragment) in new AdobeLiveCycle designer.

Sijin_Chandran
Active Contributor
0 Kudos

Hello All,

I am facing issue while utilizing the Fragment based Adobe From approach for building an Output Layout.

I am taking Content Form "MM_PUR_PURCHASE_ORDER" as an example. I downloaded the same from 'Maintain Form Template' Fiori App along also downloaded Master Form "APOC_DEMO_FORM_MASTER_AE" along with it.

As you are aware a Master Form is used/referred inside a Content Form, so that we can use the Master Pages defined inside a Master Form while building a Content Form. So Master Form is kind of reusable collection of Master Pages.

Please see the below screenshots of Content Form "MM_PUR_PURCHASE_ORDER" in Adobe Live Cycle designer to get the picture:

Now coming to the 'bdyMain' SubForm of this Layout where we would be referring the Master Pages.

This issue is when I try to change this to the Local Master Page of this Content form i.e.(Master Pages)>mstDummy.

I hope I was able to make everyone understand my issue. You can try this if you have got latest Adobe Live Cycle designer and S4 HANA system access to download these Form Templates. Is this a bug of Adobe Live Cycle designer. The above highlighted scenario can happen, while designing Content Forms there are chances we might accidentally remove the reference and if we cannot bring it back then we would need to start building from scratch. If we are pretty careful then its okay. Helpful comments much appreciated.

Thanks,

Sijin

Sijin_Chandran
Active Contributor
0 Kudos

Additional comments: I have referred couple of blogs available here regarding this. But in those blogs they are just adding Logo to Master Form->Master Pages and no further information regarding the above scenario.

Accepted Solutions (1)

Accepted Solutions (1)

PascalBremer
Advisor
Advisor

Hi Sijin,
Adobe livecycle designer does not support referenced master pages in their autocomplete dialog.
If this is a critical requirement for you, please get in touch with SAP support, so we can forward this request to our partner Adobe.

In regards to your original question:
What to do, when you have accidentally deleted the master page reference (mst1 for example) ?
1. Click on the page on the content, where you want to change the master page.
2. Click on the menu bar: View=>XML Source
3. Replace the text mstDummy => mst1 (make sure you do not change the xml structure itself)

4. Switch back to Design View and save

Sijin_Chandran
Active Contributor
0 Kudos

That works like a Charm!

But while editing the XML code it gave a warning message saying, (Not able to upload screenshot)

"Do you want to save your changes to the XML source? Some changes may cause the form to stop functionality correctly"

Truly speaking this doesn't look good. But it works and must say I would have never been able to find this for sure.

Considering your below comment:

"If this is a critical requirement for you, please get in touch with SAP support, "

I actually opted for a Standalone form and am using the local Master Pages now.

I truly believe rather getting this done via XML Source code changing we should get that option from the Screen itself, because there can be cases where user creates a New Subform in Design View and they want to give its Pagination reference to the Master Page inherited from the Fragment of a Master Form. This issue definitely limits the flexibility. Just my thoughts 🙂

Thanks,

Sijin

rpscg
Explorer

I have encountered this exact same issue with a custom purchasing form (not the purchase order). Unless you have a pre-delivered form that has the master page references already declared, there is no other way to point to the correct page without xml editing.
It is obviously not fixed three years later.
I do not know why you need customers to state that they need a feature and report it to Adobe - the product does not work for the use case of custom forms, which is something SAP offers, not Adobe. Most of us don't know "what good looks like" (it's certainly not this though), so unless we stumble across the correct error report we are not going to know it can even be done. Net result, people back off to create standalone forms as that is all that really works. Which is a shame as I appreciate the holistic output management approach but it's got too many flaws for me to recommend it.

rpscg
Explorer
0 Kudos

I have found a way to make this work without editing the XML.

The host form has a group area called "Master Pages" and so has the fragment you wish to provide the master page layouts. If you have three pages in your fragment called Page1, Page2, LastPage, all you have to do is put page nodes with the same names in the top "Master Pages" group. At runtime, the base form master pages section is overlaid by the fragment master pages and if the names line up, the content can be directed to those pages.

When you add those page nodes to the base form master page set they become available in the Pagination lookup - so you can address them 'by proxy' with this indirection.  

Answers (0)