Low-Code Platforms: Custom Fit, Fast Results
TAKE NOTE (Insights into Emerging Technology)
At $634 billion, software will be the largest component of business tech spending in 2017 and beyond, according to Forrester.
Meanwhile, 25 to 30% cloud adoption rates will turbocharge software spending, as more and more companies look for faster ways to build unique applications to compete and win in the digital economy.
Perhaps this is why over 80% of CIOs said that they expect to play more active roles in digital transformation initiatives over the next two years, according to research by MWD advisors.
The bad news?
Approximately 69% of these respondents fear their teams are struggling to keep up with ever-rising digital expectations.
This is the magic of low-code development—the reason why more and more companies are embracing the visual design and drag-and-drop functionality of modern low-code platforms to:
> Accelerate digital transformation.
> Develop powerful business apps faster then ever.
> Create unique custom software—with fewer resources
and at much lower cost.
Modern low-code capability is now a strategic necessity across all industries. Low-code-powered digital transformation rocks at starting small and making a difference quickly, according to the experts at MWD. But it’s a mistake to believe that all low-code platforms are created equal.
In their white paper—Low-code platforms, ideal to drive rapid digital transformation—MDW cuts through the low-code hype
UNDER DEVELOPMENT (Information for Developers)
SAP Screen Personas : Customizing On-Screen Table Controls
Using Screen Personas to Simply On-Screen Tables
Last month we covered how to hide fields, merge tabs, and customize the look an feel of standard SAP transactions. This allowed us to simplify many parts of the screen but noticeably left out on-screen tables, which are often the most complex parts of SAP transactions. SAP Screen Personas has an entire tab dedicated to table personalization within the editor. These features allow users to hide, rearrange, pin or rename any column. In addition, users can add stylistic improvements or add conditional formatting to highlight important scenarios about their data. To illustrate the capabilities of SAP Screen Personas’ table personalization, we will revisit customizing VA02. Initially, we see that the Item Overview tab has a huge number of fields, many of which an average user would never use (see below)
As an added pain, as the user scrolls to the right through these fields, they have no control over which fields are lost and which remain in focus. The good news is by using Screen Personas we can address all of these issues for tables. We can even highlight certain scenarios we are particularly concerned with using conditional formatting.
To begin editing our table, we enter the Persona editor mode and select our table. Once the table is selected, our first step will be to “pin” the columns we always want to display. To do this, we select these columns and click the “Move to Fixed Area” option on the function bar. (To perform the opposite action, we could have selected a column already in the Fixed Area and clicked “Move to Scrollable Area”
Q&A (Post your questions and get the answers you need)
Q. In productive system of my Webdynpro Application I get a 500 Internal Server Error when calling a RFC Function. In test system everything works fine. Can you give me a hint, what the problem could be? I have no idea where to start the search!
A. When you call an RFC-enabled function module, an error may occur. Depending on the error handling of the application, the following situations may arise:
1. The application does not catch the RFC exceptions (in the error situation, the ABAP runtime error CALL_FUNCTION_REMOTE_ERROR occurs; for more information, see Note 97522).
2. The application catches the RFC exceptions but does not provide the caller with the RFC message text that was received; instead, it provides a fixed message text that does not help with analyzing the error.
As you mentioned it works in the TEST environment, so more than likely the RFC is being called by a user that is either locked or even not defined in Production.
Here are a couple of steps you can take:
– Check the dumps on each side in their respective systems using ST22
-In the program issuing the calling RFC, add the following two additional exception types:
SYSTEM_FAILURE
This exception reports all failures and system problems on the remote machine.
COMMUNICATION_FAILURE
This exception is raised when a connection or communications failure occurs. It does not report system problems (for example, abnormal termination) that occur on the remote machine.
The code looks like this…
CALL FUNCTION Remotefunction
DESTINATION Dest
EXPORTING…
IMPORTING…
TABLES…
EXCEPTIONS
SYSTEM_FAILURE = 1 MESSAGE msg
COMMUNICATION_FAILURE = 2 MESSAGE msg
The system sets the message variable (msg) to the system message. You can then display the message or log it in a file. You should not try to interpret message text in your program.