BinaryAugust 28, 2019 at 1:16 am #5537
I know it is not recommended to mix Dojo with Spark Ui in the same coach but we had no other choice in this case. Everything works fine but the css seems to be broken.
Is there a chance for an easy fix? See the error message attached for an example.
Kind regardsSPARK SupportAugust 28, 2019 at 5:33 am #5539
If the CSS is breaking, then there must be a naming collision between the dependencies. You would need to determine which classes are clashing and override the conflict by adding !important to your own CSS copied from the original SPARK styling. You can also add a custom class to the control through the HTML Attributes, and develop a higher priority CSS Selector. This will not be an easy fix unfortunately, most likely requiring plenty of trial and error.
Finding a BPM UI equivalent, or developing a custom control might be less of an effort than restyling the toolkit. Please feel free to reach out to our Sales Team if you feel your customer would benefit from an Engagement with Salient.
Stephen P.BinaryAugust 29, 2019 at 1:34 am #5541
Thank you Stephen! As a quick fix / work around I got it done by changing the type of the effected elements from Dojo to Spark Ui 🙂SPARK SupportAugust 29, 2019 at 6:18 am #5543
That sounds like the best possible solution! We have many customers looking to migrate process applications with older toolkit dependencies to BAW and the new stock UI (formerly SPARK UI). The best answer is always to replace all controls, include those in nested within custom views.
You must be logged in to reply to this topic.