Mobile Taxonomy: Connected Content of Child Topics

[Christof Brockh]

Hi,

My customer has two taxonomies. One used in the now mobile app and one used in employee center.

The mobile taxonomy is a clone of the ec taxonomy and was not changed yet.

On desktop the parent topics show the connected content of their child topics.

In the now mobile app however, this is not the case.

A mobile user has to open the topic, which actually holds the content to see the requests and articles.

Does anybody know how to change the behavior on the now mobile app to be the same as in the portal?

Is it configurable at all? Where would I configure this?

Thank you in advance

Christof

[Nishant12 · Accepted solution]

Hi @Christof Brockh , 

This was intentional behaviour from the product. 
Portal rolls up content from child topics whereas on mobile the content doesn't roll up to parent topic. 

If you need to change this behaviour, you need to set a system property (name : sn_ex_sp.u_allow.rollup.mesp )to true 

thanks,
Nishant K 

[Nishant12 · Accepted solution]

Hi @Christof Brockh , 

This was intentional behaviour from the product. 
Portal rolls up content from child topics whereas on mobile the content doesn't roll up to parent topic. 

If you need to change this behaviour, you need to set a system property (name : sn_ex_sp.u_allow.rollup.mesp )to true 

thanks,
Nishant K 

[Christof Brockh]

Hi Nishant,

thank you for your answer.

I did not find the system property on the instance, so I created it.

The behavior in the now mobile app did not change.

I guess it is because of caching.

Is there anything I can do, do reset the cache server side?

[Nishant12]

Can you please tell me the employee center plugin version . 

To reload the cache you can navigate to /cache.do and reload cache .

[Nishant12 · Accepted solution]

This property has been shipped in version 30.0.2 of the employee center. So if you are in the previous version this property might not be available and adding the property manually also will not work as the code associated with the property will not exist. Please upgrade to 30.0.2.