Using custom card with OVP pattern - any limitations?

[Jelena]

We're planning to use the custom component cards with overview page pattern (as described in this blog).

Judging by the blog and comments, looks like pretty much anything can be implemented in these cards. But I'm wondering if there are actually any limitations / restrictions with regards of custom cards in OVP? To those who used this, have you encountered any issues?

Also, we plan to use OVP for different groups of users and use card authorizations to determine which card should be shown or not. Could there be any problem with this for the custom cards?

We're trying to avoid any unexpected issues down the road, so looking for advise from those who've already implemented this. Thank you!

[AshishAnand · Accepted solution]

Hello Jelena,

Yes technically you have a lot of scopes to have your own implementation but those should work with OVP standard application. Card authorization should work with custom cards also. Something which a developer should keep in mind while developing a custom card:

1. The developer is responsible for sizing, resize and drag and drop of custom card.
2. All the data flow should be via annotations. You should avoid annotations or manifest card settings which is not supported by OVP standard card.
3. Should follow MVC religiously. use of byId() method should be avoided.
4. Avoid excessive use of custom CSS.
5. Never override or use any code provided by OVP standard in your custom card code.
6. Define your cards strictly based on the documentation https://sapui5.hana.ondemand.com/#/topic/6d260f7708ca4c4a9ff45e846402aebb

Hope it helps 🙂

Thanks and Regards

Ashish

[Jelena · Accepted solution]

Thank you, Ashish!