Blog

Icons can be assigned to views in order to better communicate the purpose of a particular form at a glance.

By default, view headers will display the view label, description, and the first field value. The background will be a solid color.

Scrolling down will move the header text to the toolbar.

Let’s assign an icon to the views of Customers controller in the Northwind sample app.

Switch back to the Project Designer. In the Project Explorer, switch to the Controllers tab. Double-click on “Customers / Views / editForm1”.

Icons can be defined by specifying the icon library and the icon name. Spaces are replaced with dashes.

Assign an icon to the view in the Tags property, and press OK to save.

Double-click on “Customers / Views / createForm1”. Assign an icon to this view as well.

On the toolbar, press Browse. Navigate to the Customers page, and select a customer. The header will display the new icon on the left side. The background will show a large greyed out version of the same icon.

Scrolling down will reveal a smaller version of the icon.

Close the form, and press the New icon. The create form will display the assigned icon as well. The picture below shows the create form on a smaller device or window.

DotNetNuke (DNN) is a popular content management system build with Microsoft ASP.NET technology with the loyal following. Developers love the ease of customization and native support for Microsoft Development Tools. Nevertheless it is difficult to build complex user interface when large number of data entry screens is required. Code On Time application generator provides DotNetNuke Factory project designed to produce native DNN module with complex data entry screens created directly from your database.

Applications for DNN created with Code On Time have a Classical (Desktop) user interface and cannot run outside of the portal on their own. Over the past years we have developed a new powerful user interface called Touch UI. This user interface relies on the pages with special structure to enable execution on both mobile and desktop devices. It is impossible to plug such pages into the DNN portal without disrupting its core functionality.

Our product used to offer SharePoint Factory project designed to create native web parts for this portal in the fashion very similar to DotNetNuke Factory. In fact, some core capabilities were shared between the two. Microsoft has greatly changed SharePoint portal starting with SharePoint 2013. It became impossible to incorporate custom web parts directly in the pages of this portal. Instead, developers have to create dedicated applications, which run in a completely isolated environment frequently on a different physical server. The output of the custom code is displayed in an <iframe> element allocated on the SharePoint page for the purpose of integration. The custom code must use OAuth protocol for authentication if access to the host site data such as current user is required.

Starting with release 8.5.12.0 we are retiring SharePoint Factory project and make it possible to integrate any Web Site Factory or Web App Factory project in Software-as-a-Service mode into SharePoint Online (http://sharepoint.com), SharePoint 2013, and above. A free web part from Microsoft Office Store (https://store.office.com/en-us/app.aspx?assetid=WA104380704) makes it easy to integrate Code On Time apps in SharePoint sites (http://codeontime.com/learn/sharepoint/add-in/configuration).

We will bring Touch UI and SaaS integration technology to DotNetNuke users in release 8.5.13.0.

Developers will create either Web Site Factory or Web App Factory project on top of their database. The database will have its own security system to maintain users and roles. The following will be performed when application is ready for integration:

1. Application will be deployed to either dedicated server or on the machine where DNN portal is running.

2. Developer will generate a secret key stored in the application database.

3. Developer will install a Data Connector for Cloud On Time module into the portal and have it configured on portal page.
1. The module will be placed on the page of the portal.

2. The secret key generated in step #2 will be specified in the module properties.

3. URL of the application page or its root address must be specified.

4. Optional DNN tokens can be listed in the Data Connector configuration.

4. Data Connector will communicate with the the application instance when the page is rendered by the portal on the server:
1. Connector will make a server-to-server request to the application passing the encrypted secret key, name of the user, roles, and  optional values of DNN tokens.

2. Application will confirm the secret key, process tokens, and return login token to the Data Connector.

3. If the portal user does not exist in the application database, then the user with the same name and random password is created.

4. User roles in the application database are synchronized with the portal roles.

5. Data Connector will render an <iframe> element in the output of the page with the login token in the URL pointing to application page.

5. The page with the <iframe> will be rendered by the web browser on the client device.

6. Application will perform single-sign-on for the current user with the help of the login token in the URL of the <iframe>.

Universal Business Applications created with Code On Time and Cloud On Time will work both on their own and also in SaaS mode within DotNetNuke, Microsoft SharePoint Online, and Google G-Suite. If a hosted UBA is accessed directly, then the hosting environment will perform user authentication, which makes possible using apps on mobile devices outside of the host environment.

Code On Time will continue to ship with DotNetNuke Factory. If developers have existing projects of this type, then they may choose to continue creating native DNN Factory apps with Classical user interface.