Using Version Management

Question 1

Question: How can you view the history of your app?

Answer 1

Answer: You can view the history of your app from within the Mendix Developer Portal or Studio Pro.

Question 2

Question: What are the four types of events you can see in the Mendix Developer Portal’s history?

Answer 2

Answer: In the Mendix Developer Portal’s history, you can see Commits, Created tags, Created branch lines, and Deleted branch lines.

Question 3

Question: What information is displayed for each event in the Mendix Developer Portal’s history?

Answer 3

Answer: For each event in the Mendix Developer Portal’s history, you can see the avatar of the actor, a message, the date and time of the event, the name of the actor who triggered the event, the line of the app where the event was triggered, the used Mendix Studio Pro version (except for tag events), the revision number after the event, and related user stories.

Question 4

Question: What types of events can you see in Mendix Studio Pro’s history?

Answer 4

Answer: In Mendix Studio Pro’s history, you can see Commits and created branch lines.

Question 5

Question: What information is displayed for each event in Mendix Studio Pro’s history?

Answer 5

Answer: For each event in Mendix Studio Pro’s history, you can see

the revision number,
a symbol indicating the type of change,
the author of the event,
the date of the event,
the time of the event,
the message of the event,
related user stories,
and the changes in the model and on disk (repository).

Question 6

Question: What is the purpose of Mendix’s default database for local deployment?

Answer 6

Answer: Mendix’s default database for local deployment allows you to use a built-in database, reducing dependence on external databases.

Question 7

Question: How can you share your database with your team in Mendix?

Answer 7

Answer: You can share your database with your team by creating a snapshot of your data via Mendix Studio Pro and then adding the snapshot to the deployment directory of your app.

Question 8

Question: Where can you find the option to add a snapshot of your data in Mendix Studio Pro?

Answer 8

Answer: You can find the option to add a snapshot of your data in Mendix Studio Pro by navigating to the Version control menu: Version control > Add a snapshot of your data.

Question 8

Question: What is the benefit of sharing a database snapshot with your team?

Answer 8

Answer: Sharing a database snapshot with your team saves time and helps reproduce app behavior, as team members can use your dataset for testing.

Question 9

Question: What types of conflicts can occur when collaborating on an app in Mendix?

Answer 9

Answer: Conflicts in Mendix can be related to the model (document conflicts) or other documents in the repository (app conflicts).

Question 10

Question: How can you resolve document conflicts in Mendix?

Answer 10

Answer: To resolve document conflicts in Mendix, you should identify the differences between the updated and local versions, connect with the team member who made changes, and decide which version to use. You can view both versions and choose ‘Resolve using theirs’ in Studio Pro.

Question 11

Question: What are the two main types of document conflicts in Mendix?

Answer 11

Answer: The two main types of document conflicts in Mendix are modify-modify conflicts (when both parties modify the same document) and modify-delete conflicts (when one party modifies an element that was deleted by another).

Question 12

Question: How can you prevent document conflicts from occurring in Mendix?

Answer 12

Answer: To prevent document conflicts in Mendix, make agreements with your team members, perform regular updates and commits, separate work tasks, and establish a domain model foundation at each sprint.

Question 13

Question: How can you open an older revision of an app in Mendix Studio Pro?

Answer 13

Answer: To open an older revision in Mendix Studio Pro, you need to create a branch from that revision and then open that branch in a new session. This allows you to view and analyze the older revision without making changes to it.

Question 14

Question: What are the three ways to create branches in Mendix?

Answer 14

Answer: You can create branches in Mendix using revisions of the mainline, revisions of another branch line, or tagged versions.

Question 15

Question: When might it be useful to create a branch in Mendix?

Answer 15

Answer: Creating branches in Mendix is helpful when you want to continue developing functionality without affecting the running app or when separating hotfixes from ongoing feature development.

Question 16

Question: What is the purpose of the “Port fix” option in Mendix’s merge changes functionality?

Answer 16

Answer: The “Port fix” option allows you to move specific parts from a branch line to the mainline in exceptional cases, such as moving a single feature from a branch into production.

Question 17

Question: When do you typically use the “Merge feature branch” option in Mendix?

Answer 17

Answer: You use the “Merge feature branch” option in Mendix when the development on a branch line is completed, and you want to merge the entire branch into the mainline.

Question 18

Question: What is the “Advanced merge” option in Mendix used for?

Answer 18

Answer: The “Advanced merge” option in Mendix allows you to merge various revisions of either the mainline or a branch line into the selected type of line.

Question 19

Question: When might you need to perform a reverse merge of changes in Mendix?

Answer 19

Answer: You might need to perform a reverse merge in Mendix when you want to revert to an older version of the app or undo specific changes. It’s done by specifying start and end versions.

Question 20

Question: Why is it a good practice to delete branches in Mendix?

Answer 20

Answer: Deleting branches in Mendix helps maintain control over your branches and keeps your development environment clean. It’s especially important after a branch has been successfully merged into another branch or the mainline.

Question 21

Question: What does Mendix do by default when you enable Team Server?

Answer 21

Answer: By default, Mendix provisions an SVN (Subversion) environment when you enable Team Server, handling tasks like daily backups and operational management.

Question 22

Question: What is the benefit of setting up your own SVN server in Mendix?

Answer 22

Answer: Setting up your own SVN server in Mendix gives you more control over your app deployment directory and allows for greater customization.

Question 23

Question: What additional option becomes available in the Version Control menu after enabling private version control?

Answer 23

Answer: After enabling private version control in Mendix Studio Pro, you’ll have access to the “Upload to Version Control Server” option in the Version Control menu.

Question 24

Question: How can you enable private version control in Studio Pro?

Answer 24

Answer: To enable private version control in Studio Pro, go to Edit > Preferences > Version Control > Enable private version control.

Question 25

Question: What do you need to configure when using your own SVN server as a private version control option?

Answer 25

Answer: When using your own SVN server, you’ll need to configure the server address in the “Private server” option within the Version Control menu.

Question 26

When working in an app with version control, which concept would you use to share your database with your team?

Answer 26

By creating a data snapshot and adding it to the deployment directory of your app.

Question 27

What type of conflict occurs when you and your colleague both modified the microflow implementing the delete behavior?

Answer 27

Modify-Modify

Question 28

Which of the below listed definitions can be applied to explain what does a tagged version mean?

Answer 28

A revision that has been used to build a Mx deployment package.

Question 29

Which function is used to merge a complete branch into the mainline and is only available on the main line?

Answer 29

Merge feature branch

Question 30

Which of the below mentioned options can be used to merge revisions into and from all lines, main line or branch line?

Answer 30

Advanced merge