Update doc about TWA #467

willy-ahva · 2017-01-27T10:39:33Z

Re organize menu and pages.

solivier · 2017-01-30T10:16:35Z

reference/activity_manager/widget_extension_points.rst

+________
+
+With the Activity Manager feature comes a widget in the dashboard. The goal of this widget is to display the
+completeness for contributors and owner. Displayed data are contextual. That means that the completeness is not the same


It means the completeness ?

grena

Small comments, then GTM

grena · 2017-01-30T10:11:33Z

reference/activity_manager/widget_extension_points.rst

+________
+
+With the Activity Manager feature comes a widget in the dashboard. The goal of this widget is to display the
+completeness for contributors and owner. Displayed data are contextual. That means that the completeness is not the same


grena · 2017-01-30T10:12:11Z

reference/activity_manager/widget_extension_points.rst

+
+With the Activity Manager feature comes a widget in the dashboard. The goal of this widget is to display the
+completeness for contributors and owner. Displayed data are contextual. That means that the completeness is not the same
+for each contributor and for the owner. Contributor sees completeness in terms of their own permissions. The owner sees


Contibutors see (...)

grena · 2017-01-30T10:13:45Z

reference/activity_manager/widget_extension_points.rst

+With the Activity Manager feature comes a widget in the dashboard. The goal of this widget is to display the
+completeness for contributors and owner. Displayed data are contextual. That means that the completeness is not the same
+for each contributor and for the owner. Contributor sees completeness in terms of their own permissions. The owner sees
+the completeness of all the project perimeter.


the real full completeness of family requirements

Or I don't know, but "the completeness of all the project perimeter" is not clear to me :)

grena · 2017-01-30T10:15:19Z

reference/activity_manager/widget_extension_points.rst

+    # src/PimEnterprise/Bundle/ActivityManagerBundle/Resources/config/form_extensions/widget.yml
+    extensions:
+        activity-manager-widget-project-selector:
+            module: activity-manager/widget/project-selector


You can add above this line:

The module of your extension that should be declared in a requirejs.yml file

solivier · 2017-01-30T10:17:22Z

reference/activity_manager/widget_extension_points.rst

++++++++++++
+
+Unlike the others, the activity manager widget has been done with the Product Edit Form architecture, so that it is
+more customizable and maintainable. That allowed us to create some extension points thanks to target zones.


It allowed us .... ?

grena

Fix then GTM :)

grena · 2017-03-09T13:56:31Z

cookbook/teamwork_assistant/activate_loggable_step.rst

+How To Log Memory Usage In Calculation Steps
+============================================
+
+We created the


IMOH, it could be nice have a kind of short "intro".

Why could we have to log memory usage ?

What are calculation steps?

What will I read in this doc?

grena · 2017-03-09T13:59:18Z

cookbook/teamwork_assistant/calculation_step.rst

@@ -1,8 +1,18 @@
 Add A Calculation Step
 ======================

+Before saving a project a job is launched in background. This job is composed by calculation steps. Each calculation step
+is used to execute an action between the project and a product. For example, we extract data from the product to add
+information in project. For custom development you may need to add your own calculation step.


Cool for the intro :)

grena · 2017-03-09T14:00:51Z

cookbook/teamwork_assistant/index.rst

@@ -5,4 +5,5 @@ How To Customize Teamwork Assistant (Enterprise Edition)

  Customize notifications <customize_notification>
  Add a calculation step <calculation_step>
+  How log calculation step <activate_loggable_step>


grena · 2017-03-09T14:02:13Z

reference/teamwork_assistant/behat_permission_summary.rst

+In the case you extended the Teamwork Assistant, you may want to check that you didn't broke basics features. You can
+have a look to the `Setup Behat part`_ to learn more about how to run our functional tests.
+
+Because the Teamwork Assistant heavily uses permissions we created a custom catalog that we use in our test features.


(...) heavily uses permissions, we created (...)
(missing comma)

grena · 2017-03-09T14:02:47Z

reference/teamwork_assistant/behat_permission_summary.rst

+have a look to the `Setup Behat part`_ to learn more about how to run our functional tests.
+
+Because the Teamwork Assistant heavily uses permissions we created a custom catalog that we use in our test features.
+Here is summary about permissions we use in our catalog. This catalog has been modified in few scenario but it is still


Here is a summary

grena · 2017-03-09T14:04:15Z

reference/teamwork_assistant/project_completeness.rst

+Project Completeness Format
+___________________________
+
+One normalized the completeness looks like this:


Once normalized, (...)

grena · 2017-03-09T14:05:02Z

reference/teamwork_assistant/project_completeness.rst

-completeness per user. Guessing impacted user groups is not a big deal and can be done during project creation to gain
-completeness calculation time and scalability.
+The advantage is that the regularity of the pre-processing data updating can be adjusted as required with this command.
+Before to use this you should have a look to the scalability guide.


Before using this

grena · 2017-03-09T14:05:32Z

reference/teamwork_assistant/project_completeness.rst

-during the night for many projects as we don't pre-process all the catalog but only products concerned by projects.
-As it's faster, the regularity of the pre-processing data updating can be adjusted as required.
+during the night for many projects as we don't pre-process all the catalog but only products concerned by projects and
+products that as been updated.


that has been

grena · 2017-03-09T14:06:44Z

reference/teamwork_assistant/project_creation.rst

+notify users concerned by the project.
+
+For each product we need to identify the user groups that have the rights to edit the product, once all the products
+have been checked we send a notification to the concerned users (aka the contributors).


(...) have been checked, we send (...)
(missing comma)

grena · 2017-03-09T14:09:25Z

reference/teamwork_assistant/widget_extension_points.rst

+
+With the Teamwork Assistant feature comes a widget in the dashboard. The goal of this widget is to display the
+completeness for contributors and owner. Displayed data are contextual. It means that the completeness is not the same
+for each contributor and for the owner. Contributors see completeness in terms of their own permissions. The owner sees


Contributors see completeness depending on their own permissions

willy-ahva force-pushed the AMS-144 branch from 7d2cf14 to c91fcfe Compare January 27, 2017 14:07

solivier reviewed Jan 30, 2017

View reviewed changes

grena approved these changes Jan 30, 2017

View reviewed changes

solivier reviewed Jan 30, 2017

View reviewed changes

willy-ahva changed the base branch from master to 1.7 March 7, 2017 16:21

willy-ahva force-pushed the AMS-144 branch from c91fcfe to 9a10b70 Compare March 7, 2017 16:23

willy-ahva added 6 commits March 7, 2017 17:29

AMS-144: Add AM widget extension points doc

27adbfb

Fix TWA quotes in cookbook

5825c5d

Add intro on TWA behat part

c33c019

Move calculation step in project creation reference

3c01bda

Update calculation step cookbook

e950f27

Update project completeness from TWA

90450a4

willy-ahva force-pushed the AMS-144 branch from 9a10b70 to 90450a4 Compare March 9, 2017 10:10

Update mistakes in TWA doc

dace817

willy-ahva changed the title ~~AMS-144: Add AM widget extension points doc~~ Update doc about TWA Mar 9, 2017

mickaelandrieu approved these changes Mar 9, 2017

View reviewed changes

grena approved these changes Mar 9, 2017

View reviewed changes

Willy added 2 commits March 9, 2017 15:31

Prepare TWA scalability guide

ff5aea3

Fix typo TWA

ea083e0

willy-ahva merged commit e023b29 into 1.7 Mar 9, 2017

willy-ahva deleted the AMS-144 branch March 9, 2017 15:56

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update doc about TWA #467

Update doc about TWA #467

willy-ahva commented Jan 27, 2017 •

edited

solivier Jan 30, 2017

grena left a comment

grena Jan 30, 2017

grena Jan 30, 2017

grena Jan 30, 2017

grena Jan 30, 2017

solivier Jan 30, 2017

grena left a comment

grena Mar 9, 2017

willy-ahva Mar 9, 2017

grena Mar 9, 2017

grena Mar 9, 2017

grena Mar 9, 2017

grena Mar 9, 2017

grena Mar 9, 2017

grena Mar 9, 2017

grena Mar 9, 2017

grena Mar 9, 2017

grena Mar 9, 2017

Update doc about TWA #467

Update doc about TWA #467

Conversation

willy-ahva commented Jan 27, 2017 • edited

Choose a reason for hiding this comment

grena left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

grena left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

willy-ahva commented Jan 27, 2017 •

edited