Hi David,
Thank you for reading this post. Currently, I have java portlets and have
some questions converting them to iViews. I have the iView conditions
listed below with my questions:
<u><b>iView Conditions:</b></u>
<b>1. Usage of Correct Naming Conventions:</b> If possible, can you show me a sample of
the correct naming conventions?
<b>2. Single Sign On:</b> If possible, can you please elaborate more on this and possibly provide
an example?
<b>3. Session State (During the entire usage of an iView, session state
and transaction integrity must be maintained)</b>. If possible, can you please elaborate more on this and possibly provide an example?
<b>4. Browser Independence (An iView must work with all supported versions of at least one browser type supported by Enterprise Portal).</b> If possible, can you list supported versions?
<b>5. Look and Feel (The iView must present data in the Enterprise Portal
look and feel and allow for the different personalization options that
are possible with the SAP Enterprise Portal).</b> If possible, can you please elaborate more on this and possibly provide an example?
<b>6. Error Messages (The iView must be implemented in a way that provides
default/ relevant/ meaningful error messages)</b> If possible, can you please elaborate more on this and possibly provide
an example?
<b>7. No Hard-Coded Paths </b> I understand this but just to make sure, can
you possibly provide an example?
<b>8. Special Characters (iViews must be able to depict reserved HTML
characters)</b>
If possible, can you please elaborate more on this and possibly provide
an example?
Thank you so much for your time and look forward to your
response.
Thank you,
Baggett