Blog

Why A Point Solution for Scheduling?

Posted by & filed under Implementing a Labor Scheduling Solution, Workforce Scheduling.

The bias for or against point solutions ebb and flow over time. Broadly speaking, many software applications deal with large volumes of data, but have fairly narrow purposes. For example, time & attendance systems focus on paying each worker for time worked. The data collection is important, but at the end of the day the system is a transactional  one and in general does not stray too far from its intended purpose. Scheduling systems, on the other hand, are engines that evolve from mathematics and operations research. The knowledge-base to create scheduling systems for complex, multiple constrained problems is different from business and data collection systems. This statement is not intended to disparage transactional systems – you would not want a mathematician build a payroll system – but the buyer should exercise great caution in assuming a time & attendance vendor has the expertise to craft a labor scheduling system suitable for complex work environments. Implementing the workplace rules is not a simple case of a string of “if-then-else” statements as found with simple staffing systems, but involves solving combinatorics with a possibility of a high number of interacting constraints. The market evidence is that with scheduling systems, point scheduling solutions remain the most robust for sophisticated applications.

Accessing Roundtable AppServers via Progress Explorer

Posted by & filed under Roundtable TSMS, Software Configuration Management.

On Unix and Linux installations, it is typical for the OpenEdge AdminServer to be owned by the ‘root’ user. However, this can cause problems when a normal user (like your designated RTB administrator) needs to bounce the Roundtable AppServer. Generally you do not hand out root access to everyone, but if they do not have root access they cannot connect via the Progress Explorer. What to do?

This is perfect use-case for the –admingroup option of the prodasv command. Using this option, you can control who can connect to the AdminServer via group membership. This will allow non-root users to connect and start/stop the Roundtable AppServers.

For example:
$DLC/bin/proadsv –start –port 1234 –adminport 1235 –admingroup root:rtbadmin

In this example, users in the root and rtbadmin groups can connect as needed to manage the Roundtable AppServer.

For more information about Roundtable TSMS, Software Configuration Management for Progress OpenEdge development, contact Roundtable sales or visit www.roundtable-tsms.com.

 

WeCUG Meeting

Posted by & filed under Roundtable Events, Roundtable TSMS, Software Configuration Management.


Click this link to view our event photo album.
 

The QAD West Coast User Group provides support to one another in the implementation and utilization of QAD Enterprise Applications. The User Group meetings will be of an educational nature, as well as a means of communication with QAD Inc. on common issues of interest. Click this link to visit the QAD West Coast User Group’s web page.

 

Progress Partner Conference

Posted by & filed under Roundtable Events, Roundtable Team, Roundtable TSMS.

Click this link to view our event photo album.
 

The Progress Software Partner Conference is designed for business leaders from our application partners, OEMs, and systems integrators and will provide innovative thought leadership, strategies for growth, networking opportunities with your peers, industry powerhouses, and key analysts and Progress leaders. Click this link to visit the Progress Software Partner Conference event page.

 

Continuous Integration Using Roundtable TSMS

Posted by & filed under Roundtable TSMS, Software Configuration Management.

The Roundtable TSMS API and proxy framework allows for much flexibility in your continuous integration strategy while providing means to automate development and deployment processes. Expert Thomas Hansen can demonstrate exactly how. If you missed his presentation last Fall, you can still download it and the featured appSolute Roundtable TSMS Automation Toolkit. 

To download the presentation …
Click this link.

To download the appSolute Roundtable TSMS Automation Toolkit …
Click this link to download the appSolute Roundtable TSMS Automation Toolkit for 11.x.
Click this link to read the release notes for the appSolute Roundtable TSMS Automation Toolkit for 11.x.

For more information about Roundtable TSMS, Software Configuration Management for Progress OpenEdge development, contact Roundtable sales or visit www.roundtable-tsms.com.

 

Duplicate Workspace PCODE Object Names

Posted by & filed under Roundtable TSMS, Software Configuration Management.

Did you know?
Starting with Roundtable TSMS 11, the requirement that Workspace PCODE Objects be uniquely named has been relaxed. This means that you can have duplicate PCODE Objects as long as they exist in different Product Modules and do not contain a physical part that conflicts with the physical parts of another Object. This change in behavior eliminates the need to create alias Objects, although there are still valid use-cases for Object aliases. Since this is a change in behavior from prior releases, this repository-wide setting must be enabled.

To enable … 
Choose Help > About from the Roundtable TSMS Tabletop. The About Roundtable window appears. In the Allow Non-Unique field, type “yes” to enable non-unique objects.


Click thumbnail for a full image.

For more information about Roundtable TSMS, Software Configuration Management for Progress OpenEdge development, contact Roundtable sales or visit www.roundtable-tsms.com.