Opplak advies voor zelfklevend karton

Hieronder geven wij voor het opplakken van foto's, posters, papier, etc... enkel tips, zodat u een zo goed mogelijk resultaat behaalt. Voor het opplakken kunnen de volgende materialen gebruikt worden:

1. KAPAFIX 5 of 10 mm
2. Zelfklevend karton 0.8, 1.5 of 2 mm
3. Zelfklevend PVC 1mm

U dient voordat u met het aanbrengen van uw foto begint, de zelfklevende plaat altijd na te kijken op eventuele onrechtmatigheden.
Vooraf de plaat schoonmaken, zodat overtollig stof boven op de schutlaag wordt verwijderd, de foto afvegen en dan aanzetten.

Nooit zelfklevend materiaal gebruiken als het net binnen is of als het in een koude ruimte ligt, dit geldt ook voor de foto. U dient ervoor te zorgen dat het opplak materiaal en de foto in dezelfde ruimte liggen zodat beide kamertemperatuur hebben, dit om plooien te voorkomen.

U neemt het opplak materiaal en veeg met uw hand erover om te controleren of de plaat schoon is idem bij de foto aan de achterkant. Onrechtmatigheden of stofdeeltjes zijn vaak niet te zien maar met uw hand voelt u alles, dus bij twijfel niet verwerken. U snijd ongeveer 8 cm van de schutlaag af en plakt deze opnieuw op maar dan ongeveer 15 mm van af de rand. u legt de foto nu op het schutvel en legt deze gelijk aan de randen en plakt dan de foto op de zelfklevende rand van 15 mm vast. Nu gaat u eerst het 8 cm schutvel daarna het resterende verwijderen en de foto over de hele breedte voorzichtig vast wrijven, hierna geleidelijk de schutlaag wegnemen en met gelijkmatige druk de foto aanbrengen met zachte doek.

Let op: Luchtinsluiting of plooien veroorzaakt door het niet correct aanbrengen van de foto kunnen bijna nooit gecorrigeerd worden.

Houdt er rekening mee dat polystyreen of de foto statisch zijn dus dat u werkt in een zo schoon mogelijke ruimte. Van de rondzwervende stofdeeltjes en haartjes in de ruimte vindt binnen een oogwenk een aanzienlijk deel een plekje tussen uw opplak werk.

Bij hoge temperaturen boven de 40 graden Celsius zal bij polystyreen zeker blaasvorming optreden.
Direct zonlicht of etalageverlichting moet vermeden worden zodat de polystyreen niet boven deze temperatuur zal komen.

In onderstaand voorbeeld wordt een foto opgeplakt met ruimte voor een passepartout.

Opplakken foto met passepartout rand.

Tips:

1. Aangezien het opplakken enige ervaring eist, raden wij aan om eerst een test te maken
2. Plak originele kunstwerken, waardevolle documenten en gelimiteerde oplages niet op

Mendix abbreviatens / prefix types for Microflows

There is no standaard for name convention of microflows within Mendix. During the time there are some best-practises about using name convention of the microflows.  Below there is a list of microflows name convention for the different type of microflows.  

Prefix type	Meaning	Comment
AD_	After Delete
BD_	Before Delete
ACr_	Before create
BCr_	Before create
ACo_	After commit
BCo_	Before commit
IVK_	Invoke
VA_	Visual Attribute	These microflow have visual attributes as output/return
OC_	On Change	(do not use, use OCh)
OCh_	On Change
DS_	Data Source	This microflow returns an Object or a lijst of Objects as Output/return
SE_	Scheduled Event
EVT_	Event handlers	These microflows are attached to Event handlers
NAV_	Navigation	Called from navigation (menu item)

Tips:

Name convention:

• MF triggers by an action : <prefix type>_<action to execute>
• MF that does something: <action to execute>

When you have a MF which is called by VA_ and OCh_, then the following:

• MF should be created with name <action to execute>
• VA_ --> Call MF <action to execute>
• OCh_ --> Call MF <action to execute>

RM3 Proof Of Concept for connecting C to java RM3 Engine

The Retail Mix & Match Module (RM3) Engine is a promotion rule engine that is specialized  in processing promotions. A promotion can be buy one get one or get 10% discount. To avoid coding these promotions direct in the POS/register system or Webshop, the RM3 is invented. Besides the flexibility the RM3 Engine also very fast in processing promotions. RM3 Engine can be used as java API or as a servlet. The RM3 Engine servlet can run on nearly any application server that is based on java.

To proof that the RM3 Engine could also run on a POS system, that is build on C technology a Proof of Concept is executed.

Proof Of Concept starting point:

• Connect with a C program to the RM3 Engine
• A minimum of 2000 promotions should be active
• A minimum of 100.000 items should be part of the promotions
• Discount results should be displayed per invoice line.

After a few days, we had the Proof of concept ready. The result was a C program that connected to the RM3 Engine and executed the promotion processing. The results were amazing for the performance. Calculating the promotions for an invoice with about 20 invoice lines took less than 100 milliseconds.

The following steps were executed by the C program:

• starts a JVM instance,
• Create RM3 Engine instance.
• Loading 2000 promotions, which were based on 100.000 items.
• Validate promotions
• Push the invoice header information to the RM3 Engine
• Push the invoice line information to the RM3 Engine
• After each invoice line the RM3 Engine was started to calculate the promotions
• At total
• Start the RM3 Engine again for final calculation
• Print invoice including discount information on invoice line level.

Mendix and SQL Server: Initializing the ConnectionBus failed

After installing Mendix and SQL Server it happens most of the time that running a mendix application the following message appears:

Message: Initializing the ConnectionBus failed.
Cause: Error on initializing database connection.
Stack trace: com.mendix.m2ee.api.AdminException: Initializing the ConnectionBus failed.
at com.mendix.core.MxRuntime.H(SourceFile:472)
Caused by: n: Error on initializing database connection.
at bz.b(SourceFile:218)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host localhost, port 1433 has failed. Error: "Connection refused: connect. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.".

You need to start "SQL Server Configuration Manager"
Go to Start --> Microsoft SQL Server --> Configuration Tools --> SQL Server Configuration Manager

When it opens go to "SQL Server Configuration Manager" --> "SQL Server Network Configuration" --> "Protocols for SQLExpress".

1. Where you'll find the Protocol TCP/IP, if disabled then Enable it.
2. Double click on TCP/IP, You'll find its properties and select the "IP Address" tab. In this tab Remove All the TCP Dynamic Ports and add value 1433 to all TCP Port
3. Restart your SQL Server via "SQL Server Services" --> "SQL Server" --> Restart

Change TCP/IP Disabled to Enabled

Set TCP Dynamic Ports to 0 and TCP Port to 1433

After this, the Mendix application can be started.

Mendix performance optimization for batch processing.

For some projects we needed to do batch updates or clone records.With Mendix 4, there is the possibility to commit a list entity objects.By using this feature it will improve the performance a lot.

In Mendix 3 it is done like the picture below.

Clone item without optimization

Note: In Mendix 3 it is not possible to create and update attributes at the same time, two activities are needed.
Explanation of the Microflow steps above. This example is limited to process 1000 records.

1. Retrieve 1000 records
2. For every record
1. Create new record including update attributes, commit and refresh.

With Mendix 4, this can be improved. Performance improvement of 50% can be reached.

Explanation of the Microflow steps above. This example is limited to process 1000 records.

1. Create a empty list
2. Retrieve 1000 records
3. For every record
1. Create new record including update attributes (no commit and no refresh)
2. Add new record to the list
4. Finally commit the list including refresh.
1. Refresh is needed when data needs to be displayed within screen.

In the example above the duration went from 9 seconds to 3.5 seconds.

When much more records needs to be processed it is advised to do it in batches. This can be done by setting the limit and offset at retrieve of the database entity. After the list is commited, clean the list and retrieve a new set of records from the database (see second activity in the Microflow).
Processing too many records at the same time can give memory overflow errors.

tip: When you have entities with more than 10 attributes it could be useful to use the Java clone function within the community commons from Mendix the App Store.