piyushrajput / teamspaces Goto Github PK

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

When the "Edit Team Profile" button is clicked, if the list of profile
displayed is higher than the current page, Firefox and Safari fixed this
problem by adding a scroll bar in to the page, but IE doesn't

Although than Firefox and Safari fixed by their self, we must to find a
better way to fix this problem in all browsers

Search module
     * Concerned about the space needed for the page title overlapping the
search module area.
     * Didn't initially realize that the searches were contextual per tab
     * In adv. Search, can a user search for people with a particular
competency and a rating of 5 and above?
     * Not clear what field "keyword" would be searching. [nn] A solution
is to change the default description to "name, competency, company or title"


 Overlay (I.e. new announcement)
     * Review patternforce for overlay design. [nn] Design based off of
modal dialogs and adheres to the pattern.


 Announcement
     * WYSIWYG editor in new announcement overlay. Concerns raised about
users having the ability to break the visual hierarchy of posts in the
Announcement overview page. Announcement titles should always be the
largest font to maintain visual order.
           o Suggestion: Provide only a few font-size options which are all
smaller than the title font size


 Wiki
     * Designers often post screenshots to a Wiki for review by peers. In
the current flow, the user would have to upload the image to a webserver
and then enter a URL to link it in the wiki. Too cumbersome. Google sites
has a streamlined solution for this flow.


 Teams
     * Right modules for people was easier to read. The right module on the
Teams page has too much white space between the each item. Doesn't look
like they are group together.
           o Suggestion: Implement a similar module design to people.
           o Suggestion: Try reducing the white space between each item in
the block


 General notes
     * "[Teams] must be seeded for this to be valuable." 

The following features was no implemented in the "Implement sharing for
Gantt UI" Task previously resolved.

- Creator of the task can edit the task .

- Better control for manager . owner of a task.

- change cursors when the drag are locked 

After clicking on the "Edit/Insert" button at the "WikiPageEdit" page, the
progress bar at the "Image Property" overlay stays forever

It's just happens in Safari 

The following components use an onSumbit on apex:form tag. We need to
remove the onsubmit so that we can remove the apex:form in another task to
reduce the page size. Each apex:form tag includes a viewstate variable in
the html and makes the page much later.

Here are the following components that need to be changed:

TeamsOverlayNewDiscussion.component
TeamsOverlayNewMilestone.component
TeamsOverlayNewTask.component
TeamsWidgetAttachments.component
WikiNewPageWidget.component

This is the first in a series of tasks to remove the number of view states
on the page in order to make the application run faster.

DO NOT USE ONSUBMIT on a form to complete this solution. Make sure you
solution is encapulated within each component.

MAKE SURE YOU TEST ALL INSERT FLOWS ON THE TEAM DETAILS BEFORE MARKING THIS
CLOSED 

Comments
Marcos Solari - 07/Nov/08 04:44 PM
lets use onClick thats encapsulated inside each one of the components. 

None

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

Review the program flow to check if it is possible to get better performance.

If on any overlay of Discussion, the "Insert/Edit" button is clicked a
critical error message is displayed


It's happens in all browsers

Why is there script or css in the pages? There should not be any and it
should all be in resources for the production version. ie style tags in
team overview should be . Style should not be defined in the pages

Comments:

Nicolas Gunther - 25/Apr/08 12:52 PM
HTML: http://svn.dynalias.com:8080/browse/COLLABSUITE-670

Correct the code to eliminate all the compiler warnings.

Comments:

Mathias Montossi - 02/Dec/08 05:02 PM
The part of the application I changed has not compiler warnings. 

List Filter - does a full table scan. we cannot highlight the letters of
the filter b/c it does a full table scan and as the # of teams enlarges it
will break the 1000 team limit on the list.

For prevent asynchronic errors I suggest the following:

- Save every attempt to show the window. The first attempt when is hide
will be the success one.
- For hide the window, there must be the same number of attempts to show
it. The last attempt will be the success one.

To finish this issue there must be checked all the calls to the window and
if it's possible find a automatic way to control it.

Comments:

Mathias Montossi - 27/Nov/08 01:14 PM
Any asynchronic call need it by any controller use a automatically
implementation to manage the loading window. The implementation is done, I
need to review the calls the other parts of the application.

None

Fill in the contents of the Installation wiki page for the installation
from a managed package.  This includes the page overrides and the admin
steps in the teamspaces admin area.

In some cases there is possible to resolve the situation using components
of the Flex SDK and not using custom alternatives. The idea is check the
application to find this cases and change the implementation to use the
Flex SDK components.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

Change the code to prevent leaving requests to change the current cursor.
If there are some forgotten, the newest attempts to change it could fail.

Allow users to set the number hours that represent a work day.

work day: 1 to 24 hours
work week: 1 to 7 days a week

Las vistas "Day" y "Week" no se muestran con el dia actual, como ocurre en
la vista de "Month".

Ocurre en todos los navegadores. 

If user double clicks on assignee column in the tasklist and is the first
time it does, assignees tab shows blank.

Here's what I found about TEAM timeline. Let me know if I did anything wrong.

Bugs (?)

- The Est(hrs) column is actually days, not hrs. Smallest task lasts a day.

- Sometimes when I add a dependency between tasks, the Start Date of one or
both tasks shifted.

- On the Team home page, it said a task is overdue when the task doesn't
begin till 10/7.

Inconvenience

- Can't drag and drop task down the list, only up.

- The Due Date column is a day off. For example, a 3-day task from 10/7 to
10/9 will have a due date of 10/10. In a way it is correct since the
smallest tracking unit is day, but the difference between the visual
timeline and the task list is confusing.

- The Start Date of a task is defaulted to today. If the project starts in
the future, the task can't be dragged till you change the Start Date to or
after the first date of the project.

- Doesn't take weekend into consideration. (Not much project configurations
that I can set.)

- For tasks with multiple resources, the way to adjust % dedicated are
different between the first resource (enter new value) and the second (use
the up/down arrows).

Advantage

- Good to see the reminder of tasks that are assigned to me.

In general

- I found timeline rather sluggish. I rather suffer through MS Projects for
projects with medium complexity. Project managers who are proficient with
MS Projects may not have the patience with this.

- It will work if the project plan doesn't change much after its initial
creation. 

Wiki > Wiki team Overview >Wiki Pages > Edit wiki Page

Repro Steps:

1) Copy the anchor of a wiki and paste into another (to generate an
outgoing link).
2) Paste it several times and press save.

Result:

The following message is displayed:

"Update failed. First exception on row 0 with id a0S30000000SjbpEAC; first
error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, ts.MainFeedWiki: execution of
AfterUpdate caused by: System.DmlException: Insert failed. First exception
on row 0; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY,
ts.MiniFeedAfterInsert: execution of AfterInsert caused by:
System.Exception: ts:Too many SOQL queries: 101
Trigger.ts.MiniFeedAfterInsert: line 17, column 18 Trigger.ts.MainFeedWiki:
line 59, column 13 

/apex/PeopleProfileDisplay?id=005300000017eHUAAY

    * Main: If department or division is blank, hide fields.
    * Contact Info module: If a field is blank, hide the line.
    * Contact Info module: If all IM/VoIP fields (Yahoo, Skype, AIM, Gtalk)
are empty, hide the line break at bottom of block.
    * Contact Info module: Remove the colon after "Business"
    * Competency module: If user hasn't posted a competency, display the
following message:"No competencies found."
    * Teams module: If user hasn't joined a team, display the following
message:"Marcos hasn't joined any teams yet."
    * Education should be order in reverse chronological order based on
graduation date
    * Education: add the word "of" between degree and field of study


From UE Team:
    * Competencies should be front and center
    * Education and experience could move to the right sidebar since it's
relatively static info 

Teams>Timeline

Repro Steps:

1)Click on the left border of a task (it must has a less two days of duration)

2)Drag (without Drop) the cursor to the left until the bar static size grow
up (see "wrong-resizing-step2.jpg")

3)Drag the cursor to the starting point (see "wrong-resizing-step3.jpg")

Results:

The Duration" of the task is reduced 1 day (see "wrong-resizing-result.jpg")

Update 10/7:

Also happens when clicking in the left edge of task and drag it to right. 

The user can select multiple tasks with Ctrl or Shift keys.

We can use apex:composition for widgets structure

Discussion Overview:

There are some teams which shows a number of replies distinct to 0 and the
"This Forum has no messages yet." message.

This seems to happen when a topic is deleted, it replies are not being
deleted, or it's not being reflected in the Discussion Overview.

Look at the image: "Not corresponding values in Topics.jpg".

When you drag to the left it hits Feb 08 you can not go furthur and you can
drag the image right across

The interface will look like the attached facebook interface where it will
have a list of subscriptions that are grouped by functional areas. It will
be a similar in structure to the Team profile page with multiple checkboxes
next to each line.

Here is the list of subscriptions and functional areas

Team
When a team member updates his status
When a team member is joins or leaves the team

Discussion
When a new topic is created
When a new topic or reply happens with in the team
When someone replies to a topic i authored.

Project
When a task has been un/assigned to me
When a task assigned to be has been changed by another
All task status or percent complete changes within a project
When a task has been deleted

Wiki
When a page i authored was edited
When a new page has been added to the wiki
When any changes happen to the wiki

For each grouping of update the email notification will have a different
format. ALL emails should have a link back the object they are referring to
embedded in the email

Teams
Sub:New Team Member
Body: A new team member has joined team {team name}. Please welcome {name}
to the team.

Sub:Team Member has Left the team
Body: {Name} has left team {team name}

Sub: {name} is {status}
Body: Your team mate {name} has just updated thier status to {status}

Discussion
Sub: {Message Subject} from Teamspace {Team Name}
Body:{Topic Body}

Sub: RE:{Reply Subject} from Teamspace {Team Name}
Body:{Reply Body}

.......Reponding to.....
 {Topic or Reply User is responding}


Project
Sub:{Task Name} has been assigned to you
Body: {Task Details such as name and description and start and end date}

Sub:{Task Name} has changed
Body:{show which fields have changed and what the before and after values are}

Sub:{Task name} has been removed
Body: {Task Name} has been removed

Wiki
Sub:Wiki Page {Name} with in Teamspace {team name} has been edited
Body:Wiki page {Name} has been edited by {User Name} .

Click here to see the page {link}

Sub: Wiki page {wiki name} has been added to the Team {Team Name}'s wiki
Body: Wiki page {wiki name} has been added to the Team {Team Name}'s wiki

Click here to see the page {link}

Comments
Marcos Solari - 22/Sep/08 05:23 PM - edited
0- Use the same subscribe/unsubscribe widget that's on the team details
page right now.
1- add all the booleans to the existing teamsubscriptions object.
2- when a user arrives to the subscriptions page and hits the "Save"
button, if a team subscription object does not exist, create one. That way,
if a user navigates out of that page w/o pressing save, we wont be creating
objects for no reason.

Marcos Solari - 22/Sep/08 05:23 PM - edited 0- Use the same
subscribe/unsubscribe widget that's on the team details page right now. 1-
add all the booleans to the existing teamsubscriptions object. 2- when a
user arrives to the subscriptions page and hits the "Save" button, if a
team subscription object does not exist, create one. That way, if a user
navigates out of that page w/o pressing save, we wont be creating objects
for no reason.


Juan Manuel Bessonart - 22/Sep/08 05:39 PM
Fields Added to the Object TeamSubscription__c:

TeamMemberStatusUpdated
TeamMemberJoinLeave
DiscussionNewTopic
DiscussionNewReply
DiscussionReplyToMe
ProjectTaskAssignedToMe
ProjectTaskAssignToMeChanged
ProjectTaskChanged
ProjectTaskDeleted
WikiCreatedByMeUpdated
WikiNewPage
WikiPageUpdated
[ Show » ]
Juan Manuel Bessonart - 22/Sep/08 05:39 PM Fields Added to the Object
TeamSubscription__c: TeamMemberStatusUpdated TeamMemberJoinLeave
DiscussionNewTopic DiscussionNewReply DiscussionReplyToMe
ProjectTaskAssignedToMe ProjectTaskAssignToMeChanged ProjectTaskChanged
ProjectTaskDeleted WikiCreatedByMeUpdated WikiNewPage WikiPageUpdated


Juan Manuel Bessonart - 24/Sep/08 05:29 PM - edited
Email Subscription DONE:

Teams
Sub:New Team Member
Body: A new team member has joined team {}. Please welcome {name} to the team.

Sub:Team Member has Left the team
Body: {Name} has left team {team name}

Sub: {name} is {status}
Body: Your team mate {name} has just updated thier status to {status}

Discussion
Sub: {Message Subject} from Teamspace {Team Name}
Body:{Topic Body}


Sub: RE:{Reply Subject} from Teamspace {Team Name}
Body:{Reply Body}

.......Reponding to.....
 {Topic or Reply User is responding}

Juan Manuel Bessonart - 24/Sep/08 05:29 PM - edited Email Subscription
DONE: Teams Sub:New Team Member Body: A new team member has joined team {}.
Please welcome {name} to the team. Sub:Team Member has Left the team Body:
{Name} has left team {team name} Sub: {name} is {status} Body: Your team
mate {name} has just updated thier status to {status} Discussion Sub:
{Message Subject} from Teamspace {Team Name} Body:{Topic Body} Sub:
RE:{Reply Subject} from Teamspace {Team Name} Body:{Reply Body}
.......Reponding to.....  {Topic or Reply User is responding}


Juan Manuel Bessonart - 25/Sep/08 11:46 AM - edited
Project
Sub:{Task Name} has been assigned to you
Body: {Task Details such as name and description and start and end date}

Sub:{Task name} has been removed
Body: {Task Name} has been removed

Wiki
Sub:Wiki Page {Name} with in Teamspace {team name} has been edited
Body:Wiki page {Name} has been edited by {User Name} .

Click here to see the page {link}

Sub: Wiki page {wiki name} has been added to the Team {Team Name}'s wiki
Body: Wiki page {wiki name} has been added to the Team {Team Name}'s wiki

Click here to see the page {link}

Juan Manuel Bessonart - 25/Sep/08 11:46 AM - edited Project Sub:{Task Name}
has been assigned to you Body: {Task Details such as name and description
and start and end date} Sub:{Task name} has been removed Body: {Task Name}
has been removed Wiki Sub:Wiki Page {Name} with in Teamspace {team name}
has been edited Body:Wiki page {Name} has been edited by {User Name} .
Click here to see the page {link} Sub: Wiki page {wiki name} has been added
to the Team {Team Name}'s wiki Body: Wiki page {wiki name} has been added
to the Team {Team Name}'s wiki Click here to see the page {link}


Juan Manuel Bessonart - 26/Sep/08 12:03 PM
I REIMPLEMENT, because when i edit a task, we delete the assignes and then
create news:

Project
Sub:{Task Name} has been assigned to you
Body: {Task Details such as name and description and start and end date}


Sub:{Task Name} has changed
Body:{show which fields have changed and what the before and after values are}

To do this i send some hide info about the fields that have been changed,
but the Message field length is only 255.... I have to change that...

Juan Manuel Bessonart - 26/Sep/08 12:03 PM I REIMPLEMENT, because when i
edit a task, we delete the assignes and then create news: Project Sub:{Task
Name} has been assigned to you Body: {Task Details such as name and
description and start and end date} Sub:{Task Name} has changed Body:{show
which fields have changed and what the before and after values are} To do
this i send some hide info about the fields that have been changed, but the
Message field length is only 255.... I have to change that...


Marc Ferrentino - 28/Sep/08 10:13 PM
The subscription should have the sidebar from the team details.

Marc Ferrentino - 28/Sep/08 10:13 PM The subscription should have the
sidebar from the team details.


Marc Ferrentino - 28/Sep/08 10:30 PM
looks like status emails are not getting sent out.

Make sure QA tests all of this feature

Marc Ferrentino - 28/Sep/08 10:30 PM looks like status emails are not
getting sent out. Make sure QA tests all of this feature


Ciro Sayagues - 01/Oct/08 12:46 PM
The test couldn't be completed due to some features couldn't be tested.

1-The following features have been tested and they are working fine:

Team:
-"When a team member updates his status".
-"When a team member is joins or leaves the team".

Discussion:
-"When a new topic is created".

Project:
-"When a task has been un/assigned to me".
-"All task status or percent complete changes within a project".
-"When a task has been deleted".

Wiki:
-"When a new page has been added to the wiki".
-"When a page i authored was edited".
-When any changes happen to the wiki.


2-The following features have been tested and they are not working:


Discussion:

-"When a new topic or reply happens with in the team".

Problem:

the first reply doesn't arrives.

-"When someone replies to a topic i authored".

Problem:

the first reply doesn't arrives.

3-The following features couldn't be tested:

Project:

-"When a task assigned to be has been changed by another"

it couldn't be tested because the user can't edit a Task through the app
interface (it had to be edited from the Salesforce interface, however, it
didn't work, the mails were not being sent).
see the issue COLLABSUITE-1883.

Ciro Sayagues - 01/Oct/08 12:46 PM The test couldn't be completed due to
some features couldn't be tested. 1-The following features have been tested
and they are working fine: Team: -"When a team member updates his status".
-"When a team member is joins or leaves the team". Discussion: -"When a new
topic is created". Project: -"When a task has been un/assigned to me".
-"All task status or percent complete changes within a project". -"When a
task has been deleted". Wiki: -"When a new page has been added to the
wiki". -"When a page i authored was edited". -When any changes happen to
the wiki. 2-The following features have been tested and they are not
working: Discussion: -"When a new topic or reply happens with in the team".
Problem: the first reply doesn't arrives. -"When someone replies to a topic
i authored". Problem: the first reply doesn't arrives. 3-The following
features couldn't be tested: Project: -"When a task assigned to be has been
changed by another" it couldn't be tested because the user can't edit a
Task through the app interface (it had to be edited from the Salesforce
interface, however, it didn't work, the mails were not being sent). see the
issue COLLABSUITE-1883.


Ciro Sayagues - 08/Oct/08 09:42 AM
The following feature was tested and it's working:
-"When a task assigned to be has been changed by another"

Observation:
The feature was tested by the application interface.

Ciro Sayagues - 08/Oct/08 09:42 AM The following feature was tested and
it's working: -"When a task assigned to be has been changed by another"
Observation: The feature was tested by the application interface.


Ciro Sayagues - 09/Oct/08 10:30 AM
Today the following features have been re-tested and they are not working:


Discussion:

-"When a new topic or reply happens with in the team".

Problem:

the first reply doesn't arrives.

-"When someone replies to a topic i authored".

Problem:

the first reply doesn't arrives.

Ciro Sayagues - 09/Oct/08 10:30 AM Today the following features have been
re-tested and they are not working: Discussion: -"When a new topic or reply
happens with in the team". Problem: the first reply doesn't arrives. -"When
someone replies to a topic i authored". Problem: the first reply doesn't
arrives.


Ciro Sayagues - 09/Oct/08 10:47 AM
A few features are not working but it's almost resolved.

Ciro Sayagues - 09/Oct/08 10:47 AM A few features are not working but it's
almost resolved.


Ciro Sayagues - 13/Nov/08 04:40 PM
The last time that I tested this issue, it was working mostly, but the
following features were not sending the mail on the first time it were
activated:

-"When a new topic or reply happens with in the team".
-"When someone replies to a topic i authored". 

Some parts of the code needs to be changed of layer. If some part of the
code of the view layer should be in the controller, the idea is add this
part to the currently implementation of the controller.

Comments:

Mathias Montossi - 28/Nov/08 04:34 PM
A half aprox of the application code has been checked. 

For prevent asynchronic errors I suggest the following:

- Save every attempt to show the window. The first attempt when is hide
will be the success one.
- For hide the window, there must be the same number of attempts to show
it. The last attempt will be the success one.

To finish this issue there must be checked all the calls to the window and
if it's possible find a automatic way to control it.

Comments:

Mathias Montossi - 27/Nov/08 01:14 PM
Any asynchronic call need it by any controller use a automatically
implementation to manage the loading window. The implementation is done, I
need to review the calls the other parts of the application. 

Discussion Overview

(Internet Explorer 6) The search text field is wrong shown.
Look at the image: "wrong shown search field.jpg".

There is another problem in this issue, the "Search" button must have the
background color existing in portal styles, but is having a gray
background, look at the screen shots.

Add dragging cursor when dragging items on TaskList or find a way to
customize DragManager dragging cursor.

Using the edition overlay tabs, re implement it to create a new tab.

Change the implementation of the services to allow passing handlers. The
idea is not change the logic of the services, just add this new feature.

Comments:

Mathias Montossi - 28/Nov/08 04:18 PM
Almost all the services uses the callback functions to catch asynchronic
responses. A few only left.

TEXT IDENT AND OTHERS TEXT FORMATTING:
   <p style="margin-left: 35.35pt; text-indent: -14.15pt;">
   <span style='font-family: "Times New Roman"; font-style: normal;
font-variant: normal; font-weight: normal; font-size: 7pt; line-height:
normal; font-size-adjust: none; font-stretch: normal;'>

This text formatting is not implemented yet (neither from FCKeditor,
neither copy/paste from word......) 

Remove the apex:form tags from the sidebar components on TeamDetailMarkupTop

Add a apex:form tag around the components in the TeamDetailMarkupTop.

See screenshot for sample. The screenshot are of my test code after i made
the changes

Make sure you test everything to make sure it all still works

Here's what I found about TEAM timeline. Let me know if I did anything wrong.

Bugs (?)

- The Est(hrs) column is actually days, not hrs. Smallest task lasts a day.

- Sometimes when I add a dependency between tasks, the Start Date of one or
both tasks shifted.

- On the Team home page, it said a task is overdue when the task doesn't
begin till 10/7.

Inconvenience

- Can't drag and drop task down the list, only up.

- The Due Date column is a day off. For example, a 3-day task from 10/7 to
10/9 will have a due date of 10/10. In a way it is correct since the
smallest tracking unit is day, but the difference between the visual
timeline and the task list is confusing.

- The Start Date of a task is defaulted to today. If the project starts in
the future, the task can't be dragged till you change the Start Date to or
after the first date of the project.

- Doesn't take weekend into consideration. (Not much project configurations
that I can set.)

- For tasks with multiple resources, the way to adjust % dedicated are
different between the first resource (enter new value) and the second (use
the up/down arrows).

Advantage

- Good to see the reminder of tasks that are assigned to me.

In general

- I found timeline rather sluggish. I rather suffer through MS Projects for
projects with medium complexity. Project managers who are proficient with
MS Projects may not have the patience with this.

- It will work if the project plan doesn't change much after its initial
creation. 




Comments:

Marc Ferrentino - 31/Oct/08 02:51 PM
None of these looked completed 


Mathias Montossi - 02/Dec/08 04:57 PM
- The label on TaskList is changed, now shows 'Estimate (Days)'.
- The drag and drop is fixed.
- The due date is now not a day off.
[ Show » ]
Mathias Montossi - 02/Dec/08 04:57 PM - The label on TaskList is changed,
now shows 'Estimate (Days)'. - The drag and drop is fixed. - The due date
is now not a day off.

We should use apex:composition for overlays. struct.

Edit Wiki Page

The ok button is not appearing in the Add/Edit link overlay.

Only happens in Firefox.

Las opciones de Style del FCK Editor, no estan correctamente soportadas,
fallan cuando se las combinan con otros atributos.

We should use apex:composition to app header

ajax.proxy no esta funcionando

We should use apex:composition for overlays. struct.

There is 4 overlay components in TeamDetailMarkupTop and
TeamDetailMarkupBottom.

c:TeamsOverlayNewTask
c:TeamsOverlayNewMilestone
c:WikiNewPageWidget
c:TeamsOverlayNewDiscussion

Move the 2 overlays from the TeamDetailMarkupBottom to the TeamDetailMarkupTop

Remove any apex:form from the components

Move them with in the apex:form tag in TeamDetailMarkupTop

MAKE SURE YOU REGRESSION TEST ALL OF THIS FUNCTIONALITY ON THE TEAM BEFORE
YOU CLOSE THIS ISSUE!!!!!!!!!!!!!


See screenshot of test code

Referencing Portal.css is dangerous. This is the conflict to what we had
heard from the apps team.

No Forms in components. It makes it harder for to developers to use them if
we decide to make them public. If a developer tries to use it in a page
with a form then it will throw an error

Related to:
http://svn.dynalias.com:8080/browse/COLLABSUITE-2038
http://svn.dynalias.com:8080/browse/COLLABSUITE-2040