Difference between revisions of "Scout/Tutorial/3.8/Minicrm/Table Field"

Revision as of 12:11, 25 October 2012

Scout

Wiki Home

Website

Download • Git

Community

Forums • Blog • Twitter • G+

Bugzilla

Bugzilla

Scout Tutorial
This chapter talks about table fields: tables as part of forms.
This page is an optional addition to the Minicrm Step-by-Step Tutorial and uses it as a starting point.

What is this chapter about?

We will build a new table page for the Minicrm. It will list visits (or appointments, if you want). We will build a new form to edit visits. This form will contain a table field listing the people participating.

This chapter assumes that you're pretty proficient at creating tables, forms and services. No more hand-holding. :)

Database

The Apache Derby example database already contains the following tables:

VISIT            VISIT_PARTICIPANTS
---------------  ------------------
VISIT_NR         VISIT_NR
EVT_FROM         PERSON_NR
EVT_TO           
RESPONSIBLE_NR   
CONTACT_NR

If you want to take a look at the database using a command line tool, check this section of the tutorial.

Table Page

Start with VisitTablePage and a few columns: VisitNrColumn, StartColumn, EndColumn and OrganizerColumn. Check Has Time for both StartColumn and EndColumn; set their width to 200.

Result:

(Note: We switched the Swing client to the Rayo Look & Feel.)

Outline Service

Use the StandardOutlineService and add a new operation getVisitTableData:

@Override
public Object[][] getVisitTableData() throws ProcessingException {
  return SQL.select("" +
      "SELECT V.VISIT_NR, V.EVT_FROM, V.EVT_TO, P.LAST_NAME ||', '|| P.FIRST_NAME " +
      "FROM VISIT V LEFT OUTER JOIN PERSON P " +
      "ON V.RESPONSIBLE_NR = P.PERSON_NR");
}

Have the VisitTablePage use this operation. Create an execLoadTableData operation:

@Override
protected Object[][] execLoadTableData(SearchFilter filter) throws ProcessingException {
  return SERVICES.getService(IStandardOutlineService.class).getVisitTableData();
}

Form

Create a VisitForm with a GroupBox (this just looks better). Inside the group box, add two fields: StartField and EndField, both of them dates.

Finally, add a ParticipantsField of type TableField. Use Grid H 4. More if you typically have large meetings. :)

Add a NewVisitMenu and a EditVisitMenu to the VisitTablePage.

Don't forget to pass the selected visit to the ModifyHandler in your edit menu:

@Override
protected void execAction() throws ProcessingException {
  VisitForm form = new VisitForm();
  form.setVisitNr(getTable().getVisitNrColumn().getSelectedValue());
  form.startModify();
  form.waitFor();
  if (form.isFormStored()) {
    reloadPage();
  }
}

Result:

Permission denied
If you added Permissions to your Minicrm, you will need to grant yourself the permission to create, read and update visits before you can use the menu!

Note how we did not add a column to the ParticipantsField. Before we do that, we need to write a PersonLookupCall. In the PersonLookupService, use the following SQL statement:

return "" +
    "SELECT  P.PERSON_NR, " +
    "        P.LAST_NAME ||', '|| P.FIRST_NAME " +
    "FROM    PERSON P " +
    "WHERE   1=1 " +
    "<key>   AND P.PERSON_NR = :key </key> " +
    "<text>  AND UPPER(P.LAST_NAME ||', '|| P.FIRST_NAME) LIKE UPPER(:text||'%') </text> " +
    "<all> </all> ";

Using this, we can create a ParticipantsColumn for the ParticipantsField. Make it a Smart Column and provide the PersonLookupCall we just created. Make sure the ParticipantsField table has Auto Resize Columns checked.

Result:

Make it Editable

What do we need to make this table editable? We need a way to add a new row.

Add a new link button to the VisitForm and call it NewParticipantButton.

Use this execClickAction:

@Override
protected void execClickAction() throws ProcessingException {
  getParticipantsField().getTable().addRowByArray(
      new Object[]{null});
}

If you try it, you'll note that things don't look too nice. The following screenshot adds Grid W 2 for the ParticipantsField to force column spanning and Label Visible was unchecked since the column name is the same as the label. In addition to that, check Mandatory and Has Time for both StartField and EndField.

Processing Service

Time to save things to the database! Switch to the VisitProcessService that was created for you back when you created the form.

Create:

@Override
public VisitFormData create(VisitFormData formData) throws ProcessingException {
  if (!ACCESS.check(new CreateVisitPermission())) {
    throw new VetoException(TEXTS.get("AuthorizationFailed"));
  }
 
  // FIXME: use a sequence!
  SQL.select("SELECT MAX(VISIT_NR) + 1 " +
      "FROM VISIT " +
      "INTO :visitNr", formData);
  if (formData.getVisitNr() == null) formData.setVisitNr(1L);
 
  // FIXME: need to add a smartfield for the responsible and the contact person
  SQL.insert("" +
      "INSERT INTO VISIT (VISIT_NR, EVT_FROM, EVT_TO, RESPONSIBLE_NR, CONTACT_NR) " +
      "VALUES (:visitNr, :start, :end, 0, 0)", formData);
 
  // empty names are deleted
  for (int i = 0; i < formData.getParticipants().getRowCount(); i++) {
    if (formData.getParticipants().getParticipants(i) == null) {
      formData.getParticipants().setRowState(i, ITableHolder.STATUS_DELETED);
    }
  }
 
  SQL.insert("" +
      "INSERT INTO VISIT_PARTICIPANTS (VISIT_NR, PERSON_NR) " +
      "VALUES (:visitNr, :{participants}) ",
      new TableHolderFilter(formData.getParticipants(), ITableHolder.STATUS_INSERTED),
      formData);
 
  return formData;
}

Row Status
All rows are processed according to their status. If they don't contain a participant, we mark them as deleted. By default newly created rows are marked as inserted and without a participant the INSERT statement will fail.

Missing Fields
As you can see, the form is missing two mandatory fields: one for the person responsible and one for the person contacted.

Load:

@Override
public VisitFormData load(VisitFormData formData) throws ProcessingException {
  if (!ACCESS.check(new ReadVisitPermission())) {
    throw new VetoException(TEXTS.get("AuthorizationFailed"));
  }
 
  SQL.select("" +
      "SELECT EVT_FROM, EVT_TO " +
      "FROM VISIT " +
      "WHERE VISIT_NR = :visitNr " +
      "INTO :start, :end", formData);
 
  SQL.select("" +
      "SELECT PERSON_NR " +
      "FROM VISIT_PARTICIPANTS " +
      "WHERE VISIT_NR = :visitNr " +
      "INTO :participants ",
      formData.getParticipants(),
      formData);
 
  return formData;
}

Bind Variables
The bind variables refer to session variables, fields, or columns. This is why we need to list the participants field as a bind base: this makes the participants column available.

Store:

@Override
public VisitFormData store(VisitFormData formData) throws ProcessingException {
  if (!ACCESS.check(new UpdateVisitPermission())) {
    throw new VetoException(TEXTS.get("AuthorizationFailed"));
  }
 
  SQL.delete("" +
      "DELETE FROM VISIT_PARTICIPANTS " +
      "WHERE VISIT_NR = :visitNr ",
      formData);
 
  // empty names are deleted
  for (int i = 0; i < formData.getParticipants().getRowCount(); i++) {
    if (formData.getParticipants().getParticipants(i) == null) {
      formData.getParticipants().setRowState(i, ITableHolder.STATUS_DELETED);
    }
  }
 
  SQL.insert("" +
      "INSERT INTO VISIT_PARTICIPANTS (VISIT_NR, PERSON_NR) " +
      "VALUES (:visitNr, :{participants}) ",
      new TableHolderFilter(formData.getParticipants(), ITableHolder.STATUS_INSERTED),
      formData);
 
  return formData;
}

Refactoring
Now would be a good time to move the saving of the participants field into a separate method of the process service and call it from create and store operations.

Revision as of 12:10, 25 October 2012 (view source) Asc.bsiag.com (Talk \| contribs) m (→‎Processing Service) ← Older edit		Revision as of 12:11, 25 October 2012 (view source) Asc.bsiag.com (Talk \| contribs) m (→‎Processing Service) Newer edit →
Line 165:		Line 165:

	{{note\|Row Status\|All rows are processed according to their status. If they don't contain a participant, we mark them as ''deleted''. By default newly created rows are marked as ''inserted'' and without a participant the INSERT statement will fail.}}		{{note\|Row Status\|All rows are processed according to their status. If they don't contain a participant, we mark them as ''deleted''. By default newly created rows are marked as ''inserted'' and without a participant the INSERT statement will fail.}}
−
	{{warning\|Missing Fields\|As you can see, the form is missing two mandatory fields: one for the person '''responsible''' and one for the person '''contacted'''.}}		{{warning\|Missing Fields\|As you can see, the form is missing two mandatory fields: one for the person '''responsible''' and one for the person '''contacted'''.}}

Breadcrumbs

Difference between revisions of "Scout/Tutorial/3.8/Minicrm/Table Field"

Revision as of 12:11, 25 October 2012

Contents

What is this chapter about?

Database

Table Page

Outline Service

Form

Make it Editable

Processing Service