Notice: unserialize(): Error at offset 159 of 1624 bytes in /home/o3csyjea3ono/domains/wiki.marvelit.com/html/includes/cache/LocalisationCache.php on line 1164

Warning: Invalid argument supplied for foreach() in /home/o3csyjea3ono/domains/wiki.marvelit.com/html/includes/cache/LocalisationCache.php on line 414
http://wiki.marvelit.com/index.php?title=Special:NewPages&feed=atom&hideredirs=1&limit=50&offset=&namespace=0&username=&tagfilter= MT Marvelit - New pages [en] 2024-03-29T13:55:30Z From MT Marvelit MediaWiki 1.23.2 http://wiki.marvelit.com/index.php?title=Securing_Pages_and_Folders Securing Pages and Folders 2008-11-02T20:54:55Z <p>Rmortensen: /* Securing Pages and Creating Constraints */</p> <hr /> <div>== Securing Pages, Folders and Creating Constraints ==<br /> <br /> With DASH Professional - adding security to pages can be done via the Portal Site Manager UI. <br /> Additionally, you can create custom security constraints by using the Constraints UI.<br /> <br /> == Creating Security Constraints ==<br /> <br /> Security Constraints are an easy way to create complex security rules under a single name. These constraints can than be added to a dashboard page or folder.<br /> <br /> === Updating an Existing Constraint ===<br /> <br /> To access constraints - Click DASH Administrative Portlets, Security Administration than Constraints. All the security constraints are displayed.<br /> <br /> [[Image:security6.jpg]]<br /> <br /> To edit a constraint - Click the '''Edit Constraints''' button. To Create a new constraint - click the '''New''' button.<br /> <br /> [[Image:security7.jpg]]<br /> <br /> The definitions page for the constraint is displayed. In this example - the user and manager role can view any page/folder that has this constraint assigned.<br /> If you wish to add additional roles, groups or actions - simple click the appropriate check boxes at the bottom of the page. When fisished - click the '''OK''' button<br /> <br /> [[Image:security8.jpg]]<br /> <br /> To add a new definition entry for this constraint - click the '''New''' button. A new entry is added highlighted in yellow. This is what creates a complex<br /> security rule. You can have different roles, groups and even specific users have different controls or exclude controls over a page.<br /> <br /> [[Image:security9.jpg]]<br /> <br /> In this example - we have added the user name of '''alaska''' to the users field. It is added to the constraint definition. We do not want the '''alaska''' user to<br /> have any rights under this constraint - so we will leave the actions empty. Clicking '''OK''' will save the definition entry.<br /> <br /> [[Image:security10.jpg]]<br /> <br /> The Security Constraints page is displayed. The modified constraint is highlighted in yellow. Click '''Save''' to save the modified constraint.<br /> <br /> [[Image:security11.jpg]]<br /> <br /> === Creating a New Security Constraint ===<br /> <br /> If you wish to create a brand new constraint - click the '''New''' button - a new entry is created - highlighted in yellow.<br /> <br /> [[Image:security12.jpg]]<br /> <br /> Now click the '''Edit Constraint''' button to add the definitions. Follow the above screens to create the constraint definitions. <br /> Click '''OK''' on the definitions screen - than click '''Save''' to save the constraint.<br /> <br /> [[Image:security13.jpg]]<br /> <br /> == Adding Security to a Page or Folder ==<br /> <br /> To add security to a page - you need to access the Portal Site Manager - Select DASH Administrative Portlets than Portal Site Manager<br /> <br /> [[Image:security1.jpg]]<br /> <br /> Next Navigate to your page or folder and click on the name. The Information Screen appears. Click the Security Tab. <br /> <br /> [[Image:security2.jpg]]<br /> <br /> To add a new security constraint to the page - Click the '''New''' button. To edit an existing constraint - Click on the Constraint Name and click '''Update'''.<br /> <br /> [[Image:security3.jpg]]<br /> <br /> If you click the '''New''' button, an new entry is added in the above window - it is highlighted yellow. Next - select the Security Constraint you want to add<br /> to the page via the Security Constraints pulldown menu.<br /> <br /> [[Image:security4.jpg]]<br /> <br /> The new constraint is added and is highlighted yellow. Click the '''Save''' button to add the constraint to the page or folder.<br /> <br /> [[Image:security5.jpg]]</div> Rmortensen http://wiki.marvelit.com/index.php?title=Next_Release Next Release 2008-11-02T02:45:06Z <p>Rmortensen: /* Print or Export to Applications */</p> <hr /> <div>== Q1 2009 DASH Professional Enhancements ==<br /> <br /> == Setting up Dashboard Alerts == <br /> <br /> We plan to implement a dashboard alerts function as follows:<br /> <br /> * An administrative function - that will create a KPI with applicable SQL to generate a single value.<br /> * A user accessible function - that will allow users to select the KPI, Frequency, Set Levers for the SQL, enter email address, subject line and email message<br /> * As part of #2 - the user can also select a report or chart to be included with the email<br /> * DASH will open a thread - and execute these alerts and process emails as needed. A smtp server will need to be configured to accept the emails.<br /> <br /> == Print or Export to Applications ==<br /> <br /> * Our plan here is to add small icons to the page and to a portlet - would probably be a portlet option or a printing portlet that would be placed on the page where you want to place it. <br /> * Users would click on the icon and DASH would pass the HTML from the page or portlet to the appropriate application.</div> Rmortensen http://wiki.marvelit.com/index.php?title=DASH_Professional DASH Professional 2008-11-02T02:43:03Z <p>Rmortensen: /* DASH Professional Functions */</p> <hr /> <div>== DASH Professional Functions ==<br /> <br /> '''Get all the DASH Community Functions plus:'''<br /> <br /> * [[Levers_Portlet|Levers Portlet]] , Customize levers and place them anywhere on the page<br /> <br /> * [[Editable_Report_Portlet|Editable Report Portlet]] , How to update and save MARVELit Editable Reports - data entry screens<br /> <br /> * [[HTML_Content_Portlet|HTML Content Portlet]] , add custom HTML to your dashboard pages<br /> <br /> * [[Jasper_Report_Portlet|Jasper Report Portlet]] , execute jasper reports in your dashboards<br /> <br /> * [[Excel_Imports|Import Excel Data]] , take excel data and import directly into your dashboards<br /> <br /> * [[Edit_Defaults|Add Portlet Preferences]] , Add portlet preferences via Edit Defaults Mode<br /> <br /> * [[Securing_Pages_and_Folders|Adding Security to Pages]] , Add security to your dashboard pages or folders<br /> <br /> * [[Profile_Rules|Profile Rules]] , creating specific actions upon login for certain users<br /> <br /> * [[Using_Subsites|Using Subsites]] , how to create dashboards within dashboards for certain users</div> Rmortensen http://wiki.marvelit.com/index.php?title=DASH_Community DASH Community 2008-11-02T02:42:35Z <p>Rmortensen: </p> <hr /> <div>== DASH Community Edition Functions ==<br /> <br /> * [[Administration_Portlets|Administration Portlets]] , Adding Data Sources and setting MARVELit DASH profile options<br /> <br /> * [[Chart_Portlets|Chart Portlet]] , How to update and save MARVELit Charts<br /> <br /> * [[Report_Portlet|Report Portlet]] , How to update and save MARVELit Reports<br /> <br /> * [[Meter_Portlet|Meter Portlet]] , How to update and save MARVELit Meters (dials)<br /> <br /> * [[Adding_Levers|Adding Levers]] , How to add Levers (pull down selections) and have them work on a page<br /> <br /> * [[Portlet_Variables|Portlet Variables]] , How to use Variables in Portlet configurations<br /> <br /> * [[Portlet_XML_Formatting|Format Portlets using XML]] , How to use XML tags to create custom colors, fonts, and threshholds<br /> <br /> * [[Creating_Click_Throughs|Creating Click Throughs]] , how DASH can perform drill downs - only better<br /> <br /> * [[DASH_Decorators|DASH Decorators]] , changing the look and feel of your dashboards<br /> <br /> * [[Finished_Pane|Completed Dashboard Pane in Edit Mode]]</div> Rmortensen http://wiki.marvelit.com/index.php?title=Edit_Defaults Edit Defaults 2008-11-02T02:01:32Z <p>Rmortensen: /* Setting Meter Chart Portlet Preferences */</p> <hr /> <div><br /> == Set Your Portlet Preferences via Edit Defaults Mode ==<br /> <br /> Preferences as set to enable pages to have the same behavior for all users. When a page is displayed - preferences are accessed in the database for the user/page combination. <br /> If that user has not accessed that page before than default preferences for the page are used. Thes have to be set for every portlet on a page. &lt;br&gt;&lt;br&gt; <br /> To add preferences - Click the Edit Defaults icon in the upper right corner of the any marvelit Portlet.<br /> It is next to the i (help) icon in the upper right corner of the portlet. You need to set the preferences 1 time on every portlet on every page you build.<br /> <br /> [[Image:pref1.jpg]]<br /> <br /> == Setting Meter Chart Portlet Preferences ==<br /> <br /> On a Meter Chart Portlet - open in Edit Mode (pencil icon) to obtain the ChartId (next to the Name pulldown menu) - this is the internal ID saved in the database. This ID needs to be added to the preferences when editing defaults.<br /> <br /> [[Image:pref2.jpg]]<br /> <br /> <br /> Click the edit defaults icon to display the Edit Defaults screen for the Meter Chart Portlet<br /> <br /> [[Image:pref3.jpg|400px|thumb]]<br /> <br /> Enter the following fields:<br /> <br /> '''ChartID''': Enter the ChartID when you opened the portlet in edit mode.<br /> <br /> '''BackgroundColor''': Enter a hex color for the actual meter chart background. <br /> <br /> '''ImageBackgroundColor''': Enter a hex color for the area around the meter chart.<br /> <br /> '''NeedleColor''': Enter a hex color for the needle.<br /> <br /> '''DialOutlineColor''': Enter a hex color for the thin line around the meter chart.<br /> <br /> '''ShowRangeTickLabels''': Enter true or false if you want the tick labels (range numbers) to show.<br /> <br /> '''ValueColor''': Enter a hex color for the value attributes on the meter.<br /> <br /> '''TickColor''': Enter a hex color for the tick marks on the meter dial outline.<br /> <br /> '''TickSize''': Enter the tick size in units - controls the number of ticks on the meter dial outline.<br /> <br /> '''TickLabelColor''': Enter a hex color for the range labels for the tick marks.<br /> <br /> Click the '''Save''' button to save the preferences.<br /> <br /> == Setting Chart Portlet Preferences ==<br /> <br /> On a Chart Portlet - open in Edit Mode (pencil icon) to obtain the ChartId (next to the Name pulldown menu) - this is the internal ID saved in the database. This ID needs to be added to the preferences when editing defaults.<br /> <br /> [[Image:pref4.jpg]]<br /> <br /> Click the edit defaults icon to display the Edit Defaults screen for the Chart Portlet<br /> <br /> [[Image:pref5.jpg]]<br /> <br /> Enter the following fields:<br /> <br /> '''ChartID''': Enter the ChartID when you opened the portlet in edit mode.<br /> <br /> '''Details''': Enter above, below or none to display the data from the query as part of the chart display. Appears as a miniature report.<br /> <br /> Click the '''Save''' button to save the preferences.<br /> <br /> == Setting Report Portlet Preferences ==<br /> <br /> On a Report Portlet - open in Edit Mode (pencil icon) to obtain the ReportID (next to the Name pulldown menu) - this is the internal ID saved in the database. This ID needs to be added to the preferences when editing defaults.<br /> <br /> [[Image:pref6.jpg]]<br /> <br /> Click the edit defaults icon to display the Edit Defaults screen for the Report Portlet<br /> <br /> [[Image:pref7.jpg]]<br /> <br /> Enter the following fields:<br /> <br /> '''ReportID''': Enter the ReportID when you opened the portlet in edit mode.<br /> <br /> Click the '''Save''' button to save the preferences.<br /> <br /> == Setting Editable Report Portlet Preferences ==<br /> <br /> On an Editable Report Portlet - open in Edit Mode (pencil icon) to obtain the EditableReportID (next to the Name pulldown menu) - this is the internal ID saved in the database. This ID needs to be added to the preferences when editing defaults.<br /> <br /> [[Image:pref8.jpg]]<br /> <br /> Click the edit defaults icon to display the Edit Defaults screen for the Editable Report Portlet<br /> <br /> [[Image:pref9.jpg]]<br /> <br /> Enter the following fields:<br /> <br /> '''EditableReportID''': Enter the EditableReportID when you opened the portlet in edit mode.<br /> <br /> Click the '''Save''' button to save the preferences.<br /> <br /> == Setting Lever Portlet Preferences ==<br /> <br /> On a Levers Portlet - open in Edit Mode (pencil icon) to obtain the Levers content. Levers are stored in the page.psml files and not directly in a DASH table.<br /> So the data in edit mode needs to be set in Edit Defaults mode as well.<br /> <br /> Here is a Levers Portlet displayed in Edit Mode:<br /> <br /> [[Image:proLevers6.jpg]]<br /> <br /> <br /> Click the edit defaults icon to display the Edit Defaults screen for the Levers Portlet<br /> <br /> <br /> [[Image:proLevers7.jpg]]<br /> <br /> Enter the following:<br /> <br /> '''Title''': If a titlle was entered in edit mode - enter it here<br /> <br /> '''Levers''': Enter the Levers exactly like in edit mode - with &lt;nowiki&gt;&lt;br&gt;&lt;/nowiki&gt; if used<br /> <br /> '''ShowButton''': enter true to display a button - false to not display a button<br /> <br /> '''ButtonLabel''': enter the text from the Button Label in edit mode<br /> <br /> '''Lever Default Values''': Enter a default for each lever entered in the Levers <br /> <br /> Click the '''Save''' button to save the preferences.<br /> <br /> Once these entries are made - they are automatically added to the psml file for the page and will be available for all users.<br /> <br /> == Setting Jasper Portlet Preferences ==<br /> <br /> On a Jasper Report Portlet - open in Edit Mode (pencil icon) to obtain the Jasper content. Jasper data is stored in the page.psml files and not directly in a DASH table.<br /> So the data in edit mode needs to be set in Edit Defaults mode as well.<br /> <br /> Here is a Jasper Portlet displayed in Edit Mode:<br /> <br /> [[Image:jasper9.jpg]]<br /> <br /> <br /> Click the edit defaults icon to display the Edit Defaults screen for the Jasper Portlet<br /> <br /> <br /> [[Image:jasper10.jpg]]<br /> <br /> Enter the following fields:<br /> <br /> '''title''': Enter the title to display at the top of the portlet<br /> <br /> '''sql''': Copy the SQL query from edit mode and paste it here<br /> <br /> Click the '''Save''' button to save the preferences.<br /> <br /> == Setting HTML Content Portlet Preferences ==<br /> <br /> On an HTML Content Portlet - open in Edit Mode (pencil icon) to obtain the ContentID (next to the Name pulldown menu) - this is the internal ID saved in the database.<br /> <br /> [[Image:html6.jpg]]<br /> <br /> <br /> Click the edit defaults icon to display the Edit Defaults screen for the HTML Content Portlet<br /> <br /> <br /> [[Image:html5.jpg]]<br /> <br /> Enter the following fields:<br /> <br /> '''ContentID''': Enter the ContentID when you opened the portlet in edit mode.<br /> <br /> Click the '''Save''' button to save the preferences.</div> Rmortensen http://wiki.marvelit.com/index.php?title=Excel_Imports Excel Imports 2008-11-02T01:26:31Z <p>Rmortensen: /* Access your data in your dashboard */</p> <hr /> <div><br /> == Make Excel Data Accessible in your Dashboards ==<br /> <br /> With DASH Professional - you can take excel data and make it accessible to your dashboard. This is done in four parts:<br /> <br /> * Create a properly formatted excel file with your data<br /> * Set the import preferences<br /> * Import your excel data into a DASH table in your database<br /> * Access this data in your dashboard<br /> <br /> == Format your Excel File ==<br /> <br /> The &quot;Import Data Via EXCEL&quot; portlet is, quite simply, a fast way to define a database table and records using Microsoft Excel as a prototyping system.<br /> You create tables in Excel, hand off the Excel file to the importer portlet, and the importer converts it into SQL tables with the table name of the Excel sheet name.<br /> The tables are stored in the same database that Jetspeed uses in the back end. Although it's easy to use, there are several things the user should be aware of. <br /> First, the importer doesn't automatically know what data type each column should be, so you need to specify it manually. <br /> The first row of each table should be the names of the fields, the second row should be the data types of those fields, and the third rows and later should be the actual data.<br /> <br /> Here is a very simple example of what an Excel sheet might look like if it were to contain a simple user registry:<br /> <br /> [[Image:import3.jpg]]<br /> <br /> In this example, we have just two records. The record stores the unique userid (perhaps the primary key), the username, and real name of Jean-Luc Picard and William Riker. The second row tells us what data types should be used: an integer, a fixed-length string of 8 characters, and a variable-length string of up to 32 characters.<br /> <br /> Don't forget to put data types in the second row! If we had left them out, the importer would have tried to interpret the first record as a list of data types.<br /> <br /> Most data types that are recognized by your SQL database should work with the importer. The most common data types are:<br /> CHAR(X) A fixed-length string of X characters.<br /> VARCHAR(X) A variable-length string of up to X characters.<br /> DECIMAL(X, Y) A number of up to X digits and up to Y digits after the decimal point.<br /> INTEGER An 32-bit integer ranging from -4,294,967,296 to 4,294,967,295.1<br /> �<br /> Other data types tend to vary significantly between databases, and are listed here but not explained. Many of them require arguments to indicate the capacity of the field (e.g. &quot;CHAR(10)&quot; for a string of 10 characters). Consult the documentation for your particular SQL database.<br /> <br /> The following data types are supported by JDBC, in addition to those listed above:<br /> <br /> * BIGINT<br /> * BINARY<br /> * BIT<br /> * BLOB<br /> * BOOLEAN<br /> * CLOB<br /> * DATALINK<br /> * DATE<br /> * DISTINCT<br /> * DOUBLE<br /> * FLOAT<br /> * JAVA_OBJECT<br /> * LONGVARBINARY<br /> * LONGVARCHAR<br /> * NULL<br /> * NUMERIC<br /> * OTHER<br /> * REAL<br /> * REF<br /> * SMALLINT<br /> * STRUCT<br /> * TIME<br /> * TIMESTAMP<br /> * TINYINT<br /> * VARBINARY<br /> <br /> A few data types have special meaning to the importer. These are meant as convenience functions.<br /> CHAR Equivalent to CHAR(255)<br /> VARCHAR Equivalent to VARCHAR(255)<br /> LONGVARCHAR Equivalent to VARCHAR(1200)<br /> DECIMAL Equivalent to DECIMAL(10,2)<br /> <br /> Keep in mind that the data types supported are always constrained by the SQL database that is being used. If, for example, you write the Excel file to work with Oracle, it may not work on MySQL, and vise versa.<br /> <br /> Also note that any tables defined through an Excel file in this manner are saved in the same database as the DASH tables. <br /> As a result, there is a risk that a careless user of the portlet could modify one of DASH's tables, thereby breaking DASH. <br /> Extreme care should be used when setting up this portlet, to ensure that it cannot be accessed by anyone who is not an administrator!<br /> <br /> == Access the Import Portlet ==<br /> <br /> [[Image:import1.jpg]]<br /> <br /> Access the importer by selecting DASH Administrative Portlets and selecting Importer. The Importer portlet selection screen is displayed.<br /> <br /> [[Image:import2.jpg]]<br /> <br /> There is additional documentation on the importer contained in the portlet - select th i icon in the upper right corner of the portlet to display this<br /> content<br /> <br /> == Set your import preferences ==<br /> <br /> To set your import preferences - select the pencil or edit icon on the portlet. The Importer preferences page is displayed.<br /> <br /> [[Image:import4.jpg|400]]<br /> <br /> === Import Preferences: Error Handling ===<br /> <br /> '''Ignore Invalid Excel Sheets'''<br /> <br /> If set to &quot;TRUE&quot;, any sheets containing errors are ignored. If set to &quot;FALSE&quot;, an error in any sheet will prevent the entire file from being imported.<br /> <br /> In practice, an error in one sheet may not be detected until the preceding sheets have already been imported. If this happens, and IgnoreInvalidSheets is set to &quot;FALSE&quot;, the importer will attempt to undo the changes it made according to those previous sheets. However, it is NOT guaranteed that it will succeed.<br /> IgnoreDataErrors<br /> <br /> This option does absolutely nothing!<br /> <br /> '''Ignore Invalid Data Rows'''<br /> <br /> '''Excel uses 1904 based dates'''<br /> <br /> This should be to either &quot;TRUE&quot; or &quot;FALSE&quot;, according to whether your version of Excel considers the epoch to be January 1, 1900 (default on Windows) or January 1, 1904 (default on Macintosh). <br /> The default is &quot;FALSE&quot;. If you find that dates are imported incorrectly, try changing this option. Why is this an issue? Microsoft Excel supports both date windowing formats, <br /> but doesn't save any clues as to which format is being used. As a result, if this option is not set correctly, all dates will be off by 4 years.<br /> If you are producing Excel files from multiple computers to be used with the importer, it is highly recommended that you set the Excel preferences on all of the computers to the same value<br /> that the importer is configured to expect.<br /> <br /> '''Overwrite existing tables instead of appending'''<br /> <br /> If this option is set to &quot;TRUE&quot;, any tables defined in the Excel file that already exist in the database will be dropped from the database and replaced by those from the Excel file. <br /> If set to &quot;FALSE&quot;, the records from the Excel file are simply appended to the existing database table. Note that if the tables in the database and in the Excel file don't have the exact same schema, <br /> then it will not be possible to append the records from the Excel file. The importer will display an error message in this situation.<br /> <br /> === Database Browser Preferences: Data Source Type ===<br /> <br /> The mechanism to use for accessing the database. Valid options are:<br /> <br /> * jetspeed: Uses the same database that Jetspeed uses.<br /> * jndi: Uses a JNDI data source.<br /> * dbcp: Uses an SQL database via JDBC.<br /> * sso: Uses an SSO data source.<br /> <br /> The default is &quot;jetspeed&quot;.<br /> <br /> ===JNDI Settings===<br /> <br /> * JndiDatasource: The path to be passed to the JNDI driver.<br /> <br /> === JDBC/DBCP Settings ===<br /> <br /> * JdbcDriver: The fully-qualified name for the JDBC driver.<br /> * JdbcConnection: The path to be passed to the JDBC driver.<br /> * JdbcUsername: The username to pass to the database.<br /> * JdbcPassword: The password to pass to the database.<br /> <br /> === J2 SSO options ===<br /> <br /> * SSOJdbcDriver: The fully-qualified name for the JDBC driver.<br /> * SSOJdbcConnection: The path to be passed to the JDBC driver.<br /> * SSOSite: The URL to be passed to the SSO driver.<br /> <br /> === Test and Save your Importer Preferences ===<br /> <br /> Once you have made all your updates - clcik the Test button to ensure that they are correct. If errors display - correct the preferences until all errors are resolved.<br /> Click the Save button to store your preferences for the importer.<br /> <br /> == Select and Upload your Excel File ==<br /> <br /> Once you have stored your preferences, click the browse button and navigate to a properly formatted Excel file and select it. The full path to the file will be displayed in the<br /> portlet<br /> <br /> [[Image:import5.jpg]]<br /> <br /> Click the Upload button to process the import. After several seconds messages will display that either tell you that the file was processed successfully or if there were <br /> import errors.<br /> <br /> [[Image:import6.jpg]]<br /> <br /> === Common Import Errors ===<br /> <br /> * Make sure your sheet names are one word - or use the underscore &quot;_&quot; instead of spaces.&lt;br&gt;<br /> * Make sure there are no spaces in your column names - use the underscore &quot;_&quot;. Column names in your spreadsheet = column names in your table.&lt;br&gt;<br /> * Make sure that you do not bad characters in you spreadsheet - especially columns defined as integers. Make zero instead of being empty.&lt;br&gt;<br /> * Make sure column or sheet names are not SQL reserved words&lt;br&gt;<br /> <br /> === How to Troubleshoot Importer Errors ===<br /> <br /> '''Set your preferences to overwrite your data - that way during troubleshooting - your table will be dropped and rebuilt each time'''<br /> <br /> * Start small - have 1 row of data for all columns. This will usually weed out data errors - and will let you know if column names are the issue.&lt;br&gt;<br /> * If 1 row of data does not load - than something is wrong with your column names or data definitions. Start with th efirst column do an import. Keep adding columns until you get the error. The last column is the issue.&lt;br&gt;<br /> * If all columns load with 1 row of data - than you have a data issue in other data rows. Look at your spreadsheet and pay close attention to columns defined as integers or real. Dates can also be an issue. Unfortunately - the same method applies - load small amounts until you can isolate the row with bad data.&lt;br&gt;<br /> <br /> == Access your data in your dashboard ==<br /> <br /> Once you data has been uploaded - you can access it using standard SQL in all marvelit portlets. Your sheet names = table names and column names = columns in your table.</div> Rmortensen http://wiki.marvelit.com/index.php?title=HTML_Content_Portlet HTML Content Portlet 2008-10-31T04:44:35Z <p>Rmortensen: /* Set Lever by Adding Date Control Example */</p> <hr /> <div><br /> == Add HTML to Your Pages ==<br /> <br /> With DASH Professional - you can place custom HTML on any page by using the HTML Content Portlet <br /> You can utilize this portlet to do the following:<br /> <br /> 1. Add custom text to any page&lt;br&gt;<br /> 2. Add javascript to add create unique controls and data entry fields&lt;br&gt;<br /> 3. Add frames and link to other web pages for custom applications&lt;br&gt;<br /> 4. Add virtually any HTML controls to your pages.&lt;br&gt;<br /> <br /> == HTML Content Portlet ==<br /> <br /> Add the HTML Custom Portlet to any section of your pages. The portlet opens in edit mode. Enter data in the following fields:<br /> <br /> [[Image:html1.jpg]]<br /> <br /> '''Select from Saved Content''': Once a HTML Content Portlet is Saved - it is stored in a table in the DASH database. Select a value to add saved content.<br /> <br /> '''Parameter List''': Enter Lever names that will be used in the HTML Content Portlet. When you tab out of the field - default value entry boxes are displayed so you can enter default values.<br /> <br /> '''Saved Name''': Enter a name to reference the HTML Content. This is saved in the database and is displayed in the '''Select from Saved Content''' pulldown once saved.<br /> <br /> '''content''': Enter HTML or Javascript to be displayed/executed<br /> <br /> == IFRAME Example - embed Pentaho Report in DASH ==<br /> <br /> Here is a completed HTML Content Portlet that displays an iframe accessing a Pentaho Chart on a remote server. Levers are referenced in the Parameter List. The portlet displays areas for setting<br /> default values. The portlet content is saved in the database as '''pentaho1''' with ContentID = 1.<br /> <br /> The content is an html iframe command. When the page is displayed - the iframe is executed and the lever values are passed to the remote page. A Chart is generated and displayed on the DASH<br /> page. The SRC tag of the HTML Content for this example is:<br /> &lt;br&gt;<br /> <br /> &lt;nowiki&gt;src=&quot;http://demo.xxx.com/pentaho/ViewAction?solution=xxxexamples&amp;path=gidash<br /> &amp;action=chart_bar_revenue_by_productline.xaction&amp;region=$P{pRegion}&amp;years=$P{pYear}&amp;width=400&amp;height=400&quot;&gt;<br /> &lt;/nowiki&gt;<br /> &lt;br&gt;&lt;br&gt;<br /> Notice how the levers are passed to the remote page - $P{pRegion}&amp;years=$P{pYear} - When users select those levers on the page and click the button - the page is refreshed and the new values are passed to the<br /> remote page and used to generate the report.<br /> <br /> [[Image:html2.jpg]]<br /> <br /> The above portlet - displays this chart on the DASH page.<br /> <br /> [[Image:html3.jpg]]<br /> <br /> == IFRAME Example - embed Pentaho Pivot report in DASH ==<br /> <br /> Here is a similar example that displays a pentaho pivot report:<br /> <br /> [[Image:html4.jpg]]<br /> <br /> The SRC tag of the HTML Content for this example is:<br /> <br /> &lt;nowiki&gt;src=&quot;http://demo.xxx.com/pentaho/Pivot?solution=xxxexamples&amp;path=gidash&amp;action=pivot_sales_filter_region.xaction&amp;region=$P{pRegion}&quot;&gt;&lt;/nowiki&gt;<br /> <br /> == Set Lever by Adding Date Control Example ==<br /> <br /> Here is an example of setting a Lever $P{TestDate} using the Marvelit Calendar Control:<br /> <br /> [[Image:html7.jpg]]<br /> <br /> <br /> The HTML content to produce the above lever is:<br /> <br /> &lt;nowiki&gt;<br /> &lt;form name=&quot;dateform&quot; method=&quot;post&quot;&gt;<br /> Test Date: &lt;input name=&quot;TestDate&quot; type=&quot;text&quot; value=&quot;$P{TestDate}&quot; id=&quot;dateform_TestDate&quot;&gt; &lt;a href=&quot;javascript:void(0)&quot; onclick=&quot;if(self.dateform_TestDate_control)dateform_TestDate_control.fPopCalendar(document.dateform.TestDate);return false;&quot; &gt;&lt;img name=&quot;popcal&quot; align=&quot;absmiddle&quot; src=&quot;/marvelit/cal/DateTime/calbtn.gif&quot; width=&quot;34&quot; height=&quot;22&quot; border=&quot;0&quot; alt=&quot;&quot;&gt;&lt;/a&gt; &lt;iframe width=188 height=166 name=&quot;gToday:datetime:agenda.js:dateform_TestDate_control:plugins_date.jsp&quot; id=&quot;gToday:datetime:agenda.js:dateform_TestDate_control:plugins_date.jsp&quot; src=&quot;/marvelit/cal/DateTime/ipopeng.htm&quot; scrolling=&quot;no&quot; frameborder=&quot;0&quot; style=&quot;visibility:visible; z-index:999; position:absolute; top:-500px; left:-500px;&quot;&gt;&lt;/iframe&gt;&lt;input type=&quot;submit&quot; value=&quot;Go&quot; name=&quot;submit&quot;&gt;<br /> &lt;/form&gt;<br /> &lt;/nowiki&gt;<br /> <br /> == HTML Content Portlet Preferences ==<br /> <br /> Preferences as set to enable pages to have the same behavior for all users. When a page is displayed - preferences are accessed in the database for the user/page combination. If that user has not accessed that page<br /> before than default preferences for the page are used. Thes have to be set for every portlet on a page. To add preferences - Click the Edit Defaults icon in the upper right corner of the HTML Content Portlet.<br /> It is the icon next to the edit or pencil icon. The Edit Defaults Screen is displayed:<br /> <br /> [[Image:html5.jpg]]</div> Rmortensen http://wiki.marvelit.com/index.php?title=Jasper_Report_Portlet Jasper Report Portlet 2008-10-30T21:57:12Z <p>Rmortensen: </p> <hr /> <div>== Execute Jasper Reports in DASH ==<br /> <br /> With DASH Professional - you can have users execute pre-defined jasper reports from within your dashboard. This is done in four parts:<br /> <br /> 1. Enter the location of .jasper report files so DASH can find them<br /> 2. Define an entry for the report and the data source to be used<br /> 3. Establish any report groups or user, group, role permissions for the report<br /> 4. Add a portlet to a page - so users can access and execute the reports<br /> <br /> In order to have a Jasper Report executed by DASH - you will need to create a Jasper Report and successfully complile it. JasperSoft distributes an application called iReport<br /> that performs this function. As part of the report compliation process, a file is created with a .jasper extension. These files are what DASH needs to access to execute the report.<br /> <br /> How to create a jasper report and compile it is out of scope for this wiki. We are assuming that you know how to do this. For additional information - here are some helpful links:<br /> <br /> == Set Jasper Report Location ==<br /> <br /> To tell DASH where your .jasper files are located - click DASH Administration under DASH Administrative Portlets<br /> <br /> [[Image:jasper1.jpg]]<br /> <br /> The top section of that page has an entry '''Jasper Reports Folder''' Enter the path on the dashboard server where the .jasper files are located.<br /> In this example - they are all stored in the '''c:\Reports''' folder.<br /> <br /> [[Image:jasper2.jpg]]<br /> <br /> == Jasper Report Administration ==<br /> <br /> Once you have defined your Report Location - you need to define a jasper report to DASH. Select DASH Administration portlets, DASH Jasper Administration.<br /> <br /> [[Image:jasper3.jpg]]<br /> <br /> The DASH Jasper Administration page is displayed. Here you can define a report, set permissions and create report groups.<br /> <br /> [[Image:jasper4.jpg]]<br /> <br /> === Define Reports ===<br /> <br /> The top section of the page is where you define a Jasper Report. Click the edit (pencil) icon on the left of a report to edit or click the New Record link to create a new entry. The Jasper<br /> Report Entry Screen is displayed. <br /> <br /> [[Image:jasper5.jpg]]<br /> <br /> Enter the following fields:<br /> <br /> '''Title''': Enter a descriptive report title that will display on the screen for users to select.<br /> <br /> '''File Name''': Enter the name of the .jasper file for the report. This file must be in the folder specified in the Reports Folder entered on the Dash Administration Page. This name is case <br /> sensitive - make sure it is entered exactly as the file name.<br /> <br /> '''Data Source''': Select the datasource to be used for the report. Dash will execute the report against this datasource.<br /> <br /> '''Group''': Select the Report Group. Create Report Groups in the Report Group section of the page. These Groups will allow you to group reports together for users to see.<br /> <br /> Click the '''Save''' Button to save the report definition or '''Cancel''' to reset the form. '''Refresh''' is not used.<br /> <br /> === Set Report Permissions ===<br /> <br /> The middle section of the page allows you to define report permissions. Click the edit (pencil) icon on the left of a permisison to edit or click the New Record link to create a new permissionm. The Jasper<br /> Report Enter Permissions Screen is displayed. <br /> <br /> [[Image:jasper6.jpg]]<br /> <br /> Enter the following fields:<br /> <br /> '''Title''': Select the report title to be used for the permission<br /> <br /> '''User Group''': Enter the name of the user group that can access this report. See ... for information on creating User Groups in Dash.<br /> <br /> '''User Role''': Enter the name of the user role that can access this report. See ... for information on creating User Roles in Dash.<br /> <br /> '''User Name''': Enter the name of the user that can access this report. See ... for information on creating Users in Dash.<br /> <br /> Click the '''Save''' Button to save the report definition or '''Cancel''' to reset the form. '''Refresh''' is not used.<br /> <br /> === Set Report Groups ===<br /> <br /> The lower section of the page allows you to define report groups. Click the edit (pencil) icon on the left of a group to edit or click the New Record link to create a new group. The Jasper<br /> Report Enter Groups Screen is displayed. <br /> <br /> [[Image:jasper7.jpg]]<br /> <br /> Enter the following fields:<br /> <br /> '''Jasper Group''': Enter the name of the report group<br /> <br /> Click the '''Save''' Button to save the report definition or '''Cancel''' to reset the form. '''Refresh''' is not used.<br /> <br /> == Adding Reports to a Dashboard Page ==<br /> <br /> Once you have defined your reports, permissions and groups - you are ready to add reports to a dashboard page. This is done by using the Jasper Report Portlet. Add this portlet to any section of a page - just <br /> like any chart, meter or report. Click the edit (pencil) icon in the upper right corner of the portlet to add content. The portlet displays an entry screen:<br /> <br /> [[Image:jasper9.jpg]]<br /> <br /> Enter the following fields:<br /> <br /> '''Title''': Enter the title of the reports list. Use a descriptive name for users to see.<br /> <br /> '''SQL''': Enter the SQL Query to obtain a list of reports to be displayed. Use the Jasper Report Tables in the DASH Database and create a SQL query that displays a set of reports.<br /> In the example - all reports that are in report group 1 will be displayed. These are all the budget reports. You can can join to the Jasper Permissions table as well to obtain reports<br /> for specific users, groups or roles. Example SQL for this type of list would be:<br /> <br /> 1<br /> 2<br /> 3<br /> <br /> Click the '''Save''' Button to save the report definition or '''Cancel''' to reset the form.<br /> <br /> A list of reports based on the SQL entered in the portlet will be displayed. Users can clcik on the Export links to execute the report. Additionally, if your report uses parameters, <br /> add a Lever Portlet above the report list for users to select the values for the report. As long as the Lever Names match the parameters in the report - selecting values in Levers will be<br /> passed to the report.<br /> <br /> [[Image:jasper8.jpg]]<br /> <br /> == Jasper Portlet Preferences ==<br /> <br /> Preferences as set to enable pages to have the same behavior for all users. When a page is displayed - preferences are accessed in the database for the user/page combination. If that user has not accessed that page<br /> before than default preferences for the page are used. Thes have to be set for every portlet on a page. To add preferences - Click the Edit Defaults icon in the upper right corner of the Jasper Report Portlet.<br /> It is next to the edit (pencil) icons in the upper right corner of the portlet. The Edit Defaults Screen is displayed:<br /> <br /> [[Image:jasper10.jpg]]<br /> <br /> Once these entries are made - they are automatically added to the psml file for the page and will be available for all users.</div> Rmortensen http://wiki.marvelit.com/index.php?title=Levers_Portlet Levers Portlet 2008-10-29T02:08:56Z <p>Rmortensen: /* Lever Portlet Preferences */</p> <hr /> <div>== What is a Lever ==<br /> <br /> Levers are the pulldown menus that exist at the top of a dashboard pane. In DASH Community Edition, these levers are placed automatically on the page when you use the DASH page decorator.<br /> In DASH Professional - there is a Levers Portlet that allows for much more customization.<br /> <br /> To Add, Update or Delete a lever - login as an administrator, select '''DASH Administration Portlets''' and click on '''DASH Lever Administration'''<br /> <br /> [[Image:proLevers1.jpg]]<br /> <br /> == The Lever Page ==<br /> <br /> The Lever Page is displayed. This page displays all the Levers that have been added. The pencil icon on the left side of each row will edit that lever. <br /> The red circle on the right of each row will delete the lever. Click on the '''New Record''' link to enter a brand new lever into the system.<br /> <br /> [[Image:proLevers2.jpg]]<br /> <br /> == The Enter Levers Screen ==<br /> <br /> Clicking on the edit icon for a Lever or the New Record Link will display the Enter Levers Screen. Enter data into the following fields:<br /> <br /> '''Name''': - this is the name for the lever. It will be displayed on the Lever List and be referenced in SQL as $P{Name}<br /> Make it descriptive like Region, State, City, Customer - etc.<br /> <br /> '''Display Name''': - This name will appear on any page that you reference the lever. Leave this blank if you wish to use the Lever Name. You can also enter $P Values here if you wish to<br /> have the name displayed on the screen match a value selected in a previous lever.<br /> <br /> '''SQL Statement''': - enter a valid SQL query for the data source selected. <br /> This sql query must contain two values in the select clause - the first value is what is executed in the SQL for each portlet, the second appears in the Lever pull down on a dashboard pane. <br /> <br /> '''Data Source''' - This determines what data source the SQL Statement uses. Click on the pulldown menu and select a datasource. <br /> These values are the datasources entered into the data source portlet - see [[Administration_Portlets|Administration Portlets]] for additional information on adding datasources.<br /> <br /> '''Display Order''': - This field only used if you use the DASH decorator which places the levers automatically in the page. This number starts on the left - so a value of 1 will mean that this lever<br /> will display first on the page.<br /> <br /> [[Image:proLevers4.jpg]]<br /> <br /> Click the '''SAVE''' button to store the Lever or '''CANCEL''' to start over. '''REFRESH''' is not used on this screen.<br /> <br /> == Completed Lever Entry ==<br /> <br /> [[Image:proLevers3.jpg]]<br /> <br /> Here is a completed Lever Portlet entry. In this example the Name is Org1. There is no display name so the Name will appear if referenced on a dashboard pane <br /> <br /> The Query will be against the DASH data source. The query places a wildcard of 'ALL' in the lever pulldown - and if selected will insert a wildcard character of '%'.<br /> This wildcard entry will be combined with the results of the union select statement. <br /> The value Org1 is listed twice (once for portlet sql and once for the display pulldown) in the select statement. <br /> <br /> It will appear as the 1st lever from the left if the DASH decorator us used.<br /> <br /> == Lever Portlet ==<br /> <br /> In DASH Professional we have created a Lever Portlet. This Portlet allows designers more control over where levers are displayed on a page, how levers display, what order they display and default values can be specified.<br /> The Levers Portlet can be added to any section on a page just like the chart, meter and report portlet.<br /> <br /> [[Image:proLevers5.jpg]]<br /> <br /> Here is a set of levers that are displayed on a page. These were created by the following Levers Portlet.<br /> <br /> [[Image:proLevers6.jpg]]<br /> <br /> Clicking on the edit icon (pencil on upper right corner of the portlet) will display the Levers Portlet Screen. The following fields can be entered:<br /> <br /> '''Title''': Enter Text to display at the top of the Lever Portlet. The text is controlled by an entry in the marvelit.css file in the webapps/marvelit directory.<br /> <br /> '''Levers''': Enter the Lever Names to be displayed. Do not enter Display Names - they will be used when the levers are drawn. If you wish to wrap levers to appear on different lines in the portlet - separate<br /> the names by &lt;br&gt;. For example '''Org1 &lt;br&gt; Org2''' Also - the levers will display in the order entered here - the display order is ignored.<br /> <br /> '''Default Lever Values''': For every entry in the Levers field - an entry will be displayed for a default value. If you want to set a default - enter the first value in the Levers SQL Query for that Lever.<br /> for example - for Org1 - the sql is '''Select '%', 'All' union select org1, org1 from demo''' so for All to be a default - enter % or enter a value for Org1 in the Org1 default lever value field. <br /> <br /> '''Show Button''': Select yes to display a button, select no if you do not want a button to display.<br /> <br /> '''Button Label''': Enter the text top be displayed on the button.<br /> <br /> === Create a Text Entry Lever ===<br /> <br /> To create a blank entry box in the levers portlet - simply enter a lever name that has not been defined in the DASH Levers Administration page. Enter a name in the Levers Portlet - just like any other lever -<br /> just do not define it. When the levers are drawn on the page - an blank box will display with the Lever Name. The Display Name will not apply as it has never been defined.<br /> <br /> You can still set default values, use &lt;br&gt; entries. The lever can be referenced in SQL by using a $P like the other levers. Since you can enter text you may want to reference these levers in your SQL with an IN clause as well.<br /> <br /> == Lever Portlet Preferences ==<br /> <br /> Preferences as set to enable pages to have the same behavior for all users. When a page is displayed - preferences are accessed in the database for the user/page combination. If that user has not accessed that page<br /> before than default preferences for the page are used. Thes have to be set for every portlet on a page. To add preferences - Click the Edit Defaults icon in the upper right corner of the Levers Portlet.<br /> It is next to the i (help) icon in the upper right corner of the portlet. The Edit Defaults Screen is displayed:<br /> <br /> [[Image:proLevers7.jpg]]<br /> <br /> Enter the following:<br /> <br /> '''Title''': If a titlle was entered in edit mode - enter it here<br /> <br /> '''Levers''': Enter the Levers exactly like in edit mode - with &lt;br&gt; if used<br /> <br /> '''ShowButton''': enter true to display a button - false to not display a button<br /> <br /> '''ButtonLabel''': enter the text from the Button Label in edit mode<br /> <br /> '''Lever Default Values''': Enter a default for each lever entered in the Levers field<br /> <br /> Click the '''Save''' button to save the preferences.<br /> <br /> Once these entries are made - they are automatically added to the psml file for the page and will be available for all users.</div> Rmortensen http://wiki.marvelit.com/index.php?title=Portlet_Preferences Portlet Preferences 2008-08-31T21:05:27Z <p>Rmortensen: </p> <hr /> <div>Content for this page will be added by March 1, 2007. Please check back than.</div> Rmortensen http://wiki.marvelit.com/index.php?title=Editable_Report_Portlet Editable Report Portlet 2007-08-07T05:24:36Z <p>Rmortensen: </p> <hr /> <div><br /> == What is an Editable Report ==<br /> <br /> The Editable Report Portlet allows you to create portlets to update data directly in your chosen database. It is useful in a number of ways:<br /> <br /> 1. Direct data entry into transaction tables to be used in dashboards &lt;br&gt;<br /> 2. Updating of access and control information by specific users&lt;br&gt;<br /> 3. Updating of reference information such as groups, offices, regions, etc.&lt;br&gt;<br /> 4. Any other data entry or manipulation of dashboard tables.&lt;br&gt;<br /> <br /> == Getting Started ==<br /> <br /> The Data Entry Portlet works with an existing Report Portlet to display data in a list. See [[Report_Portlet|Report Portlet]] for specifics on creating a report using the report portlet.<br /> &lt;br&gt;&lt;br&gt;<br /> <br /> For Example purposes - we have created a report the lists offices. A portion of the report portlet is on the left with the resulting report on the right.<br /> <br /> <br /> [[Image:edit0.jpg]]<br /> <br /> &lt;br&gt;<br /> <br /> === Display Primary Key in Report ===<br /> <br /> An important part of the editable report is the primary key of the table to be edited. In the above report portlet - the Office_Id is the primary key of the Office table. We need to include this key in the report to be used by the editable report portlet.<br /> <br /> It is important to note - that you should establish a single column in your table and designate that column as a primary key. The editable report uses this to update and insert new rows into the table. This key element should also be set up to auto increment - that way you do not have to worry about setting the key on inserts<br /> <br /> == The Editable Report Portlet ==<br /> <br /> Now that we have created a list to use in the editable report - we can configure the portlet.<br /> <br /> <br /> [[Image:edit1.jpg|right]]<br /> <br /> '''Select Datasource''' - select the datasource to be used in the editable report<br /> &lt;br&gt;&lt;br&gt;<br /> '''Select from Saved Editable Report''' - A list of editable reports for the selected datasource will be displayed.<br /> &lt;br&gt;&lt;br&gt;<br /> '''Saved Name''' - the name to be used when you save the portlet. This name will be listed in the previous pulldown when saved.<br /> &lt;br&gt;&lt;br&gt;<br /> '''Title''' - the title to be displayed on the data edit screen<br /> &lt;br&gt;&lt;br&gt;<br /> '''Select Report''' - the name of the report portlet to be used to display data for edit or entry. In the example above it would be '''Entry Office List'''.<br /> &lt;br&gt;&lt;br&gt;<br /> '''Table''' - this is the table name in your datasource that will be edited using the editable report portlet. In the above example - we would select the office table. When you select the table - the portlet adds the columns from that table to the portlet - see next image<br /> <br /> &lt;br&gt;&lt;br&gt;<br /> [[Image:edit2.jpg]]<br /> <br /> &lt;br&gt;&lt;br&gt;<br /> When you select a table - the columns from that table are displayed. Additional columns are displayed in the portlet as well:<br /> <br /> '''Field''' - the column name from the table selected<br /> &lt;br&gt;&lt;br&gt;<br /> '''Label''' - the label to be displayed for that table column in the data edit screen<br /> &lt;br&gt;&lt;br&gt;<br /> '''Hidden''' - specifies if the column is hidden on the data edit screen<br /> &lt;br&gt;&lt;br&gt;<br /> '''Updatable''' - specifies if entries can be made in this column. If checked - a field will be displayed on the data edit screen for this column<br /> &lt;br&gt;&lt;br&gt;<br /> '''Lookup''' - a sql statement that will create a pull down menu for users to select a value. The first value in the select statement will be set as the column value. The second value will be displayed in the pulldown menu. In this example - region_id will be saved - but region (name) is displayed in a pull down menu for user selection.<br /> &lt;br&gt;&lt;br&gt;<br /> '''Default Value''' - default value for the column when saved<br /> &lt;br&gt;&lt;br&gt;<br /> '''Key Parameter''' - box will be check if this is the primary key for the table. Will automatically be checked if specified in the table definition.<br /> &lt;br&gt;&lt;br&gt;<br /> '''Detail HTML''' - section to enter detailed html that will be used instead of the default edit screen. This is a complex function and should only be used if you are an experienced html developer. See Advanced functions for additional information<br /> &lt;br&gt;&lt;br&gt;<br /> '''Cancel:''' Cancel changes and display the report.<br /> &lt;br&gt;&lt;br&gt;<br /> '''Save:''' Save changes and display the report.<br /> <br /> === Editable Report Portlet Behavior ===<br /> <br /> [[Image:edit3.jpg]]<br /> <br /> When you click '''SAVE''' - the report portlet specified in the editable report portlet will be displayed with an '''edit''' (pencil) icon to the left of each item, a '''delete''' (red circle) to the right and a '''New Record''' Link.<br /> <br /> '''Edit (Pencil)''' - click the pencil icon next to a row and that row is displayed in the data edit screen. In this example (top) the region is pre-populated in the pull down menu. The lookup in the editable report portlet executed and pre-selected the current value. Clicking SAVE will save any edits to the database - Cancel will cancel any edits. In both examples - the list of records will be displayed again.<br /> &lt;br&gt;&lt;br&gt;<br /> '''Delete (red circle)''' - click the red circle - and the row is deleted. The list of records will be displayed again with the selection removed.<br /> &lt;br&gt;&lt;br&gt;<br /> '''New Record''' - clicking the New Record link will display the data edit screen empty for entry. In this example (bottom) the screen is empty. The pulldown is populated and other updatable fields are available for entry. Click '''SAVE''' to save the new record or '''CANCEL''' to ignore the entry.<br /> <br /> == Data Entry Example ==<br /> <br /> Here is a complex data entry form. As you can see - some columns are hidden and others updatable. Lookups are used to populate two fields and default values are specified.<br /> <br /> &lt;br&gt;<br /> <br /> [[Image:Edit4.jpg]]<br /> <br /> &lt;br&gt;&lt;br&gt;<br /> <br /> This editable report displays this report<br /> &lt;br&gt;&lt;br&gt;<br /> <br /> [[Image:Edit5.jpg]]<br /> &lt;br&gt;&lt;br&gt;<br /> and this entry screen<br /> &lt;br&gt;&lt;br&gt;<br /> [[Image:Edit6.jpg]]<br /> <br /> == Setting up who can edit / delete records ==<br /> <br /> If you want to control who can edit and delete records - do the following:<br /> <br /> 1. Add a column user to each table that will be accessed by the editable report portlet.&lt;br&gt;<br /> 2. Like the above example - assign the ''' $V{user}''' variable as the default value for the user column&lt;br&gt;<br /> 3. Make sure to include the user column on the report portlet list. You can hide the column form user view if you wish by using the '''&lt;nowiki&gt;&lt;column number='7' hidden=&quot;true&quot;&gt;&lt;/nowiki&gt;''' attribute in the report portlet XML for that column.<br /> &lt;br&gt;&lt;br&gt;<br /> <br /> Adding this functionality - ensures that who creates a row - can only be the one to edit or delete it. Any user you can access the editable report portlet can see the data - but the Edit icon changes to a view (magnifying glass) icon. Clicking the View icon will display the row in the data edit screen - but there is only a '''DONE''' button displayed<br /> <br /> &lt;br&gt;&lt;br&gt;<br /> [[Image:Edit7.jpg]]<br /> &lt;br&gt;&lt;br&gt;<br /> [[Image:Edit8.jpg]]<br /> <br /> === Admin or Dataedit access to edit / delete records ===<br /> <br /> Users who have Admin role assigned will always be able to edit or delete data - regardless of who entered it.<br /> <br /> Users who have been assigned the dataedit role specified in the DASH Admin screen will also have edit and delete access to all data - but no admin functions. The role name specified in the '''Data Edit Role''' filed on this section needs to be entered as a Role [[Managing_Roles|Managing Roles]] and users assigned to that role [[Managing_Users|Managing Users]] for this function to work. <br /> &lt;br&gt;&lt;br&gt;<br /> <br /> [[Image:Admin2.jpg]]</div> Rmortensen http://wiki.marvelit.com/index.php?title=Execute_DASH_Installer Execute DASH Installer 2007-08-02T02:46:07Z <p>Rmortensen: </p> <hr /> <div>After you have downloaded the dash.zip file - unpack it into a folder on your hard drive. Two files will be displayed. dash-installer.jar and the mysql, oracle and sql server jdbc drivers. To start the install process - double click the dash-installer.jar file.<br /> <br /> [[Image:Install0.jpg]]<br /> <br /> '''STEP 1''' - The installer start screen is displayed. Click '''Next'''.<br /> <br /> <br /> [[Image:Install1.jpg|500px]]<br /> <br /> <br /> '''STEP 2''' - Accept the Apache License - Click '''Accept'''<br /> <br /> <br /> [[Image:Install2.jpg|500px]]<br /> <br /> <br /> '''STEP 3''' - Select an installation Folder - Click the '''Select Folder''' button to display a select destination folder screen. Select or create a folder for the installation. Click '''Next'''<br /> <br /> <br /> [[Image:Install3.jpg|500px]]<br /> <br /> <br /> '''STEP 4''' - Confirm Jetspeed Components - Click '''Next'''<br /> <br /> <br /> [[Image:Install5.jpg|500px]]<br /> <br /> <br /> '''STEP 5''' - Select your desired Database for DASH and click '''Next'''. The standard download contains code for Apache derby, MySQL or MS SQL. Derby is an imbedded database and will start automatically with DASH. Selecting Derby will bypass Steps 6,7 as no additional information is needed. If you wish to install on MySQL or MS SQL - click the appropriate radio button and complete Step 6 for your database.<br /> <br /> <br /> [[Image:Install6.jpg|500px]]<br /> <br /> <br /> '''STEP 6''' - If you selected MySQL or MS SQL - enter the database details. You will need to create a database for DASH - See: [[Data_Base_Preparation|Data Base Preparation]] For Instructions. If you have downloaded the PDF instructions - see the last several pages of the PDF for details.<br /> <br /> The JDBC File for either database was included in the dash.zip file. Click '''Select File''' navigate and select the mysql-connector-java-5.0.4-bin.jar file for MySQL or the jtds-1.2.1.jar file for MS SQL.<br /> <br /> <br /> [[Image:Install7.jpg|500px]]<br /> <br /> <br /> '''STEP 7''' - If you chose MySQL or MS SQL - Test the database connection by clicking '''Next'''. Resolve any connection errors by modifying the parameters in '''STEP 6.'''<br /> <br /> <br /> [[Image:Install8.jpg|500px]]<br /> <br /> <br /> '''STEP 8''' - Confirm your Installation by clicking '''Next'''<br /> <br /> <br /> [[Image:Install9.jpg|500px]]<br /> <br /> <br /> '''STEP 9''' - Click '''Install''' to begin the Installation<br /> <br /> <br /> [[Image:Install10.jpg|500px]]<br /> <br /> <br /> '''STEP 10''' - View Installation Progress<br /> <br /> <br /> [[Image:Install11.jpg|500px]]<br /> <br /> <br /> '''STEP 11''' - Installation is Complete. Click '''OK''' to leave the installer.<br /> <br /> <br /> [[Image:Install12.jpg|500px]]</div> Rmortensen