Page tree
Skip to end of metadata
Go to start of metadata

Playground and DEMO space

This is a playground and demo space for ConfiForms and ConfiDoc addons developed and supported by Vertuna LLC

Most pages provide a storage format for the demo, so you can use the free add-on from Atlassian Confluence Source Editor to import this configuration into your Confluence and see it in action

Please note, all the examples here are provided without any obligation and may or may not be incomplete or may have bugs, and we provide NO SUPPORT for these examples and demos.


 

Form for registering new vendor

 

For for registering new client

 

Basic reports

All my clients (in a table)

Name

alp
client 1
client 2
Client ABC
Client DEF
Client Me
foo_client
Name test
Sarah

 

Same as above but as a list (with totally custom layout)

alp based in location y

client 1 based in Location 1

client 2 based in Phoenix, AZ

Client ABC based in New York, NY

Client DEF based in Charlotte, NC

Client Me based in Phoenix, AZ

foo_client based in bar_location

Name test based in lOCATION Test

Sarah based in Salem, NH

 

All my vendors (in a table with name and location)

Name

Location

Vendor XYZ Phoenix, AZ
Vendor QRS Phoenix, AZ
Vendor YZA New York, NY
Vendor TUV Newark, NJ
TEST Testville
Test
Classic Consulting San Diego, CA
A a
TestVendor TestLocation
test test location
Vendor X Zagreb, CRO
test test
Tim Henson
Vendor0001 Location0001
vendor 1 location 1
bora location x
bob here
Vendor XYZ XXX
Vendor XYZT XXX
ABG XXX

 

Vendors per location

Location

Per location

Phoenix, AZ 2
New York, NY 1
Newark, NJ 1
2
Testville 1
San Diego, CA 1
a 1
TestLocation 1
test location 1
Zagreb, CRO 1
test 1
Henson 1
Location0001 1
location 1 1
location x 1
here 1
XXX 3

Clients per region

 

Vendors per region

 

 

My client (by name) with all vendors in a custom view (showing only ONE client by filter with custom layout)

 

Client ABC

Based in: New York, NY

Vendors:

Vendor XYZVendor QRS

 

Showing customers who use vendor matching a filter (vendors:*TUV)

  • Client DEF

 

 

 

 

 

"questionable" reports

  • querying through vendors about clients (not directly at least, but though custom views), as we only store one way reference in client table/form. That means: vendors form knows nothing about clients
  • Vendors used by clients (with multiselect fields (we have it for vendors) the reports might be not so flexible, values are appended automatically)

Name

Vendor QRS Vendor XYZ
Vendor TUV Vendor XYZ Vendor YZA
Vendor XYZ
Test
Vendor XYZ
Vendor0001
vendor 1
bora

Name

[count]

Vendor QRS Vendor XYZ 1
Vendor TUV Vendor XYZ Vendor YZA 1
Vendor XYZ 2
Test 1
1
Vendor0001 1
vendor 1 1
bora 1

same as above but with flattened dataset

Name

[count]

9

Name

Name

Vendor QRS Vendor XYZ Client ABC
Vendor TUV Vendor XYZ Vendor YZA Client DEF
Vendor XYZ Client Me
Test Name test
Vendor XYZ client 2
Sarah
Vendor0001 foo_client
vendor 1 client 1
bora alp

same as above but with flattened dataset

Name

Name

Client ABC
Client DEF
Client Me
Name test
client 2
Sarah
foo_client
client 1
alp

 

vendors.length with Merger table

Name

vendors.asLength

Client ABC 2
Client DEF 3
Client Me 1
Name test 1
client 2 1
Sarah 0
foo_client 1
client 1 1
alp 1

as normal table (using special function to count vendors) vendors.length with table view

Name

vendors.asLength

Client ABC 2
Client DEF 3
Client Me 1
Name test 1
client 2 1
Sarah 0
foo_client 1
client 1 1
alp 1

same but using [entry_fieldname]

Client ABC with vendors count: 2

Client DEF with vendors count: 3

Client Me with vendors count: 1

Name test with vendors count: 1

client 2 with vendors count: 1

Sarah with vendors count: 0

foo_client with vendors count: 1

client 1 with vendors count: 1

alp with vendors count: 1

In current configuration we have not created a form with locations which we can then reuse in both "vendors" and "clients". (this is certainly possible, but to simplify things we have decided to use simple text field)

 

 

  • No labels